AgentGraph
REMOTE · AGENTGRAPH-NEW.VERCEL.APP
Search 42,000+ MCP servers and agents by capability over one stateless MCP endpoint.
Available components
Last scanned (23 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1473 tokens (~133/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://agentgraph-new.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentgraph-new.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| vercel.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentgraph-new.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://agentgraph-new.vercel.app/api/mcp | HTTPS enforced | 308 | https://agentgraph-new.vercel.app/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_tools ~73
List and filter indexed tools without a ranked task query — useful for browsing by capability, provider, or protocol.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
| limit | integer | – | – |
| protocol | string | – | – |
| provider | string | – | – |
| q | string | – | Free-text substring match on name/description. |
No output schema declared.
No examples provided.
get_agent ~36
Get the full public profile of a single owner-submitted agent by id, including its reported interaction summary.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_agent_invocation ~298
Get the machine-readable invocation contract for an owner-submitted agent: whether it's directly callable, which protocol (MCP, A2A, HTTP_JSON), the endpoint, auth requirements, input/output schemas where declared, and pricing (result.pricing — { mode: "FREE" } or { mode: "FIXED", amount, amountAtomic, currency, paymentProtocol, network, platformFeeBps, paymentRecipient }). An Agent may expose more than one contract for different capabilities (e.g. one for image comparison, a separate one for free-text idea evaluation) — pass `capability` to get the one that actually serves it; without it, this returns the Agent's primary/default contract plus a `multipleContracts`/`invocationsUrl` pointer if there's more than one. Use get_agent_invocations to list every contract at once. For a FIXED/X402 contract, use get_payment_requirement to obtain a standards-compliant x402 v2 payment requirement before invoking. Owner-submitted and unverified unless verificationStatus says otherwise — AgentGraph does not call this endpoint itself; the caller invokes the provider directly and reports the outcome via the interactions API.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Optional normalized capability name — returns the contract mapped to it, if any, instead of the Agent's primary/default contract. |
| id | string | yes | Agent id (or agentgraph:agent:<id> — the plain id also works). |
No output schema declared.
No examples provided.
get_agent_invocations ~87
List every invocation contract an owner-submitted agent has declared — the unambiguous, capability-scoped view for an Agent that exposes more than one separately-callable surface. Each entry lists exactly which capabilities it serves. AgentGraph does not call any of these itself.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent id (or agentgraph:agent:<id> — the plain id also works). |
No output schema declared.
No examples provided.
get_capability ~32
Get a single capability record by id, including which tool or agent exposes it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_demand ~105
V0.4 demand intelligence: deterministic aggregates over real search telemetry — top intent concepts, top matched capabilities (rank<=10), and how many recent searches had zero currently-callable Agent in their top 10. No LLM/clustering — every result reports its sample size and window. Mirrors GET /api/demand.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 30). |
| limit | integer | – | Max capabilities to return (default 20). |
No output schema declared.
No examples provided.
get_opportunities ~135
V0.4 opportunity feed: capabilities with real recent demand (>=minSampleSize top-10 matches) sorted by weakest current callable-Agent supply first. Every entry is a real, sample-sized aggregate — see excludedForSampleSize for how many low-sample capabilities were dropped rather than shown with a misleading count. Mirrors GET /api/opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 30). |
| limit | integer | – | Max opportunities to return (default 20). |
| minSampleSize | integer | – | Minimum top-10 match count for a capability to be included (default 3). |
No output schema declared.
No examples provided.
get_payment_requirement ~222
V0.6 — for a FIXED/X402 invocation contract, returns a real, standards-compliant x402 v2 PaymentRequired object (x402Version, resource, accepts[]) built fresh from that contract's current price/network/recipient. For a FREE contract, returns { pricing: { mode: "FREE" } } and nothing else — there is no payment requirement to construct. AgentGraph is not the resource being paid for: `resource.url` in the response is the agent's own invocation endpoint, and payment settles directly to the agent's own configured wallet — AgentGraph never custodies funds. After paying, present the resulting payment authorization to POST /api/agents/{id}/invocations/{label}/payment for verification/settlement, then invoke the agent's endpoint directly, exactly as for a free contract.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Agent id (or agentgraph:agent:<id> — the plain id also works). |
| label | string | – | Which invocation contract, if the Agent has more than one (default: "default"). |
No output schema declared.
No examples provided.
get_tool ~28
Get the full public profile of a single indexed tool by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
search_agents ~118
List and filter owner-submitted agents without a ranked task query — useful for browsing by capability, protocol, owner, or verification status. Use search_capabilities for a ranked task-driven search across both tools and agents.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | – |
| limit | integer | – | – |
| owner | string | – | Substring match on owner name. |
| protocol | string | – | One of: a2a, mcp, other. |
| q | string | – | Free-text substring match on name/description. |
| verified | boolean | – | – |
No output schema declared.
No examples provided.
search_capabilities ~313
Search AgentGraph's index of real MCP servers and owner-submitted agents for ones that can perform a described task. Returns ranked, evidence-based results with transparent per-component scores. Every result includes machine-readable pricing (result.invocation.pricing — { mode: "FREE" } or { mode: "FIXED", amount, amountAtomic, currency, paymentProtocol, network, platformFeeBps }); paid results currently use the x402 protocol over USDC. Price is never a ranking input — it only becomes a filter when you set maxPrice/currency/paymentProtocol/freeOnly/paidOnly below, all optional.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Filter by normalized capability category, e.g. "database". |
| currency | string | – | Only FIXED results in this currency, e.g. "USDC" — excludes FREE results. |
| freeOnly | boolean | – | Only FREE results (includes every Tool, which has no pricing concept). |
| limit | integer | – | – |
| maxPrice | string | – | Decimal string in display units, e.g. "0.05" — includes FREE results and FIXED results priced at or below this amount. |
| paidOnly | boolean | – | Only FIXED-priced results. |
| paymentProtocol | string | – | Only FIXED results using this payment protocol, e.g. "X402" — excludes FREE results. |
| protocol | string | – | Filter by protocol, e.g. "mcp". |
| task | string | yes | Free-text description of the task to accomplish. |
No output schema declared.
No examples provided.
How do I install the AgentGraph MCP server?
AgentGraph is a hosted endpoint at https://agentgraph-new.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentgraph-new.vercel.app
claude mcp add --transport http naithan20-agentgraph 'https://agentgraph-new.vercel.app/api/mcp'
What is the AgentGraph MCP server?
AgentGraph is an MCP server listed in the public MCP registry as io.github.naithan20/agentgraph. Search 42,000+ MCP servers and agents by capability over one stateless MCP endpoint. This page covers its hosted endpoint (https://agentgraph-new.vercel.app/api/mcp).
Is the AgentGraph MCP server safe to use?
AgentGraph scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AgentGraph MCP server expose?
AgentGraph exposes 11 tools: search_capabilities, find_tools, get_tool, search_agents, get_agent, and 6 more. Their descriptions and schemas cost roughly 1,447 tokens of context every time the server is loaded.
Does the AgentGraph MCP server require authentication?
No. We connected to AgentGraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentGraph MCP server still maintained?
AgentGraph is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AgentGraph MCP server?
VerifyMCP ran 12 checks on AgentGraph, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AgentGraph: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.