What did Hlido score NCP (Natural Context Provider)?

NCP (Natural Context Provider) scored 71/100 (STEADY) in Hlido's independent, hands-on review.

Does any vendor pay Hlido for placement?

No. Hlido takes no money from the agents it rates — scoring weights stay private and the evidence behind every verdict is public.

NCP (Natural Context Provider)

Name: NCP (Natural Context Provider) review
Item: NCP (Natural Context Provider)
Rating: 71
Author: Hlido Editor

Infrastructure · tested 2026-08-07 · re-test due 2026-11-07 · by the Hlido desk, not the vendor

In short: An MCP router that fixes tool-schema overload by exposing one small discovery interface instead of every tool — a real problem, addressed plainly.

4 PASS · 1 FAIL of 5 public-surface claims

Visit NCP (Natural Context Provider) → scorecard.json

Quick answer

NCP (Natural Context Provider) scores 71/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-08-07). STEADY (71) for a real, growing problem (MCP tool-schema context overload), a correctly-shaped solution (narrow discovery interface instead of full catalogue injection), broad documented client support, and a dedicated s

Hlido Editor · 2026-08-07

NCP sits in front of your connected MCP servers and gives the AI client a single small interface for discovery and execution, so Claude Desktop or Cursor no longer loads every tool schema from every server into context. That is a genuine and worsening problem — as MCP estates grow, the tool catalogue itself becomes the dominant context cost — and NCP's answer is the right shape: search across servers, skills and resources through one narrow surface, then execute. Beyond discovery it adds code-mode orchestration (multi-step TypeScript workflows that call MCP namespaces and return structured results), scheduling for repeatable workflows, health checks, and execution records. The documentation is well-organised, with a search-intent table mapping questions to pages and explicit client guides for Claude Desktop, Cursor, VS Code, Windsurf, Cline and Continue, plus a documented security-architecture page covering runtime permissions and boundaries — appropriate for something that brokers every tool call. Two reservations. The docs contain visible SEO scaffolding ("Important product keywords covered by this documentation include MCP router, MCP tool discovery, Model Context Protocol…"), which is keyword-stuffing in a developer doc and slightly undercuts the tone. And there are no adoption figures, named users, or benchmarks quantifying the context saving — the central claim. Reviewed from the public surface.

Why STEADY

STEADY (71) for a real, growing problem (MCP tool-schema context overload), a correctly-shaped solution (narrow discovery interface instead of full catalogue injection), broad documented client support, and a dedicated security-architecture page for a component that brokers every tool call. Held below VITAL because the central context-saving claim is unquantified, there is no adoption evidence, and the docs carry visible keyword-stuffing that reads as reach for search rank rather than for readers.

Public-surface checklist

PASS Homepage loads (required)
PASS Primary value prop (required) — 'Natural Context Provider for MCP tool discovery'
PASS Cta present (required) — 'Get Started' / 'Claude Desktop Setup'
PASS Pricing or access — Open source, npm-distributed
FAIL Evidence or demo — Documentation only — no benchmark for the context saving claimed

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-208b20bd6dfeab2e-portel-dev-github-io). Our own captures — not vendor marketing material.

NCP (Natural Context Provider) — run screenshot 1 (home.png) — home.png

NCP (Natural Context Provider) — run screenshot 2 (page_VPContent.png) — page_VPContent.png

NCP (Natural Context Provider) — run screenshot 3 (pagereadme.png) — pagereadme.png

NCP (Natural Context Provider) — run screenshot 4 (pagedocs_clients_claude-desktop.png) — pagedocs_clients_claude-desktop.png

What it does well

Targets a real and worsening problem — every MCP tool schema loaded into client context
Exposes one small discovery interface rather than the full catalogue
Code mode: multi-step TypeScript workflows calling multiple MCP namespaces, returning structured results
Scheduling plus health checks and execution records in one place
Documented client setup for six clients (Claude Desktop, Cursor, VS Code, Windsurf, Cline, Continue)
A dedicated security-architecture page on runtime permissions and boundaries — appropriate for a call broker

What it fails at

The context-saving claim — the whole point — is published with no benchmark or figure
No adoption numbers, named users, or third-party validation
Visible SEO keyword-stuffing inside developer documentation
Introduces a broker in the path of every tool call: a new dependency and a new failure point
Not exercised by us; routing correctness and overhead are untested

Best for

Users running many MCP servers who are hitting context limits from tool schemas alone
Teams wanting scheduled, repeatable MCP workflows with execution records
Developers who want multi-MCP orchestration in TypeScript rather than prompt chaining

Not recommended for

Setups with a handful of MCP servers, where the broker adds cost and no benefit
Buyers who need a measured context or latency saving before adopting
Anyone unwilling to place a third-party broker in front of every tool call

Pricing & access

Pricing findable on the public surfacePASS Open source, npm-distributed (tested 2026-08-07)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-07.

Compared to

1MCP Agent

Agent relevance

API CLI MCP Behavioral-testable

Agentic-Commerce Readiness 76/100 · COMMERCE-READY

Independent readiness for agent delegation & transaction. How it’s scored · check live

An MCP server and CLI whose only consumer is an AI client — it exists to change what an agent sees. Discovery, execution and scheduling are all agent-facing.

Agent-friendly score: 9/10

Evidence

One MCP interface for discovery across servers, skills, resources and Photons — source (2026-08-07) verified
Code mode: multi-step TypeScript workflows calling MCP namespaces — source (2026-08-07) verified
Scheduling, health checks and execution records — source (2026-08-07) verified
Documented setup for six MCP clients and a security-architecture page — source (2026-08-07) verified
Any benchmark for the context reduction it exists to deliver — source (2026-08-07)

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-1+editorial-narrative-v2 · Methodology version 2026.05 · Next review due 2026-11-07

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/portel-dev-ncp.svg)](https://hlido.eu/check/?agent=portel-dev-ncp)

HTML

<a href="https://hlido.eu/check/?agent=portel-dev-ncp"><img src="https://hlido.eu/badge/portel-dev-ncp.svg" alt="Hlido trust score"></a>