Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Nexus

REMOTE · AGENTNEXUS.APP · 2 COMPONENTS · SCANNED SEP 25

180+ tested APIs, MCP servers and CLIs your agent can call. Self-service key in one call.

Available components

remote · agentnexus.app 79 remote · agentnexus.app 67
+2 this week 79 Trust /100
Trust breakdown (7 categories)

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 Security94
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2877 tokens (~479/item across 6 items; 6 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Agent Nexus MCP server?

Agent Nexus is a hosted endpoint at https://agentnexus.app/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 · agentnexus.app

# add to Claude Code
claude mcp add --transport http app-agentnexus-agent-nexus 'https://agentnexus.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "app-agentnexus-agent-nexus": {
      "url": "https://agentnexus.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "app-agentnexus-agent-nexus": {
      "type": "http",
      "url": "https://agentnexus.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.app-agentnexus-agent-nexus]
url = "https://agentnexus.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-agentnexus-agent-nexus": {
      "type": "remote",
      "url": "https://agentnexus.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add app-agentnexus-agent-nexus --url 'https://agentnexus.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  app-agentnexus-agent-nexus:
    url: "https://agentnexus.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "app-agentnexus-agent-nexus": {
      "Transport": "http",
      "Url": "https://agentnexus.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add app-agentnexus-agent-nexus -t streamable-http -u 'https://agentnexus.app/mcp'
// mcp.json
{
  "mcpServers": {
    "app-agentnexus-agent-nexus": {
      "type": "http",
      "url": "https://agentnexus.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “list_entries” rewrote its description, which is the text the model reads security
    • Tool “search_registry” rewrote its description, which is the text the model reads security
    • Tool “submit_entry” rewrote its description, which is the text the model reads security
    • Tool “discover_capabilities” rewrote its description, which is the text the model reads security
    • Tool “get_entry” rewrote its description, which is the text the model reads security
    • Schema quality: 191 → 479 ▼ functional
    • Tool coverage: 58% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 0.3.0 → 1.0.0 functional
    • “submit_entry” added an optional parameter “contact_email” cosmetic
    • “get_entry” reworded the description of “slug” cosmetic
    • “list_entries” reworded the description of “category” cosmetic
    • “list_entries” reworded the description of “page” cosmetic
    • “list_entries” reworded the description of “per_page” cosmetic
    • “search_registry” reworded the description of “category” cosmetic
    • “search_registry” reworded the description of “limit” cosmetic
    • “search_registry” reworded the description of “query” cosmetic
    • “submit_entry” reworded the description of “auth_mode” cosmetic
    • “submit_entry” reworded the description of “auth_params” cosmetic
    • “submit_entry” reworded the description of “capabilities” cosmetic
    • “submit_entry” reworded the description of “category” cosmetic
    • “submit_entry” reworded the description of “description” cosmetic
    • “submit_entry” reworded the description of “docs_url” cosmetic
    • “submit_entry” reworded the description of “endpoint” cosmetic
    • “submit_entry” reworded the description of “input_format” cosmetic
    • “submit_entry” reworded the description of “invocation_example” cosmetic
    • “submit_entry” reworded the description of “name” cosmetic
    • “submit_entry” reworded the description of “output_format” cosmetic
    • “submit_entry” reworded the description of “pricing” cosmetic
    • “submit_entry” reworded the description of “rate_limit” cosmetic
    • “submit_entry” reworded the description of “summary” cosmetic
    • “submit_entry” reworded the description of “tags” cosmetic
  • 22 Sept 26 +42
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “discover_capabilities” rewrote its description, which is the text the model reads security
    • Tool “search_registry” rewrote its description, which is the text the model reads security
    • Tool coverage: 75% → 58% ▼ functional
    • MCP protocol: unverified → fail ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
    • Tool “discover_capabilities” now declares an output schema ▲ functional
    • Tool “get_entry” now declares an output schema ▲ functional
    • Tool “list_categories” now declares an output schema ▲ functional
    • Tool “search_registry” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: excellent → good functional
    • New tool “list_entries” functional
    • New tool “submit_entry” functional
    • “discover_capabilities” reworded the description of “category” cosmetic
    • “discover_capabilities” reworded the description of “limit” cosmetic
    • “discover_capabilities” reworded the description of “min_reliability” cosmetic
    • “discover_capabilities” reworded the description of “need” cosmetic
    • “search_registry” reworded the description of “limit” cosmetic
  • 19 Sept 26 −42
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 18 Sept 26 +39
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: excellent functional
    • First check of Tool coverage: 75 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: fail functional
  • 16 Sept 26 38

    First indexed and scored.

Diagnostics

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 25 Sept 2026 · Probed https://agentnexus.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentnexus.app CN=WE1,O=Google Trust Services,C=US 14 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 ca4f8be8963844830e894f6c353367fc
SANs: agentnexus.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentnexus.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
agentnexus.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="mcp", resource_metadata="https://agentnexus.app/.well-known/oauth-protected-resource" 

Bearer realm="mcp", resource_metadata="https://agentnexus.app/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://agentnexus.app/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://agentnexus.app/mcp
Authorisation server https://upjqzuruxbvgdrheacnz.supabase.co/auth/v1

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentnexus.app/mcp Verified 200
http (plaintext) http://agentnexus.app/mcp HTTPS enforced 301 https://agentnexus.app/mcp
MCP tools · 6 exposed · ~2,460 tokens

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 →

Tool Tokens
discover_capabilities ~349

Use this when you have a goal in plain language and no idea which interface serves it (e.g. 'send a transactional email', 'query Postgres'). Returns {need, coverage, count, uncovered, note, matches[]}; each match carries slug, name, category, endpoint, auth mode and parameters, input/output formats, rate limit, pricing and a 0-100 reliability score — everything needed to call it. Never empty and never an error on a valid need: when nothing matches, coverage='none', uncovered=true and matches[] holds reliable starting points instead. Invalid input is rejected with a validation message; the registry being unreachable is returned as an error result. Parameter guidance: write 'need' as a task, not a keyword ('send a transactional email', not 'email'); leave 'category' unset unless you specifically require one layer, since the best interface for a need is often in another; raise 'limit' when you intend to compare candidates; and use 'min_reliability' (e.g. 60) only for production calls, as it can empty an otherwise useful result set. For a known keyword, slug, vendor or category, use search_registry instead.

NameTypeReqDescription
categorystring–Restrict to one interface layer. Omit to search all three (default).
limitinteger–Maximum number of matching interfaces to return, 1-20. Default 5.
min_reliabilityinteger–Drop interfaces scoring below this 0-100 reliability value. Default 0 (no filter).
needstringyesWhat the agent is trying to accomplish, in plain language. 3-300 characters, required.
NameTypeReqDescription
countnumberyes–
coveragestringyes–
matchesarrayyes–
needstringyes–
notestringyes–
uncoveredbooleanyes–

No examples provided.

get_entry ~240

Fetch the full record of ONE approved registry entry whose exact slug you already have, e.g. from a previous discover_capabilities, search_registry or list_entries result. Read-only and idempotent: the same slug always returns the same entry until its health probe changes. Returns {entry} with endpoint, auth mode and parameters, input/output formats, rate limit, pricing, capabilities, docs URL, invocation example and the latest 6-hourly health probe — the detail level the listing tools omit. This is the single-record lookup: it takes no filters and no paging. If you do not have a slug, do not guess one — use search_registry for a keyword or discover_capabilities for a plain-language need; to walk the whole catalogue use list_entries. An unknown or unapproved slug is an error, not an empty result.

NameTypeReqDescription
slugstringyesExact lowercase slug of one entry, 1-80 chars, as returned in the 'slug' field of any other tool, e.g. 'stripe-api' or 'github-mcp'. Case-sensitive, no URL and no display name; only entries with stat…
NameTypeReqDescription
entry–yes–

No examples provided.

list_categories ~122

Return the fixed taxonomy of Agent Nexus: the three interface layers it indexes ('api', 'mcp', 'cli'), each with a label, a one-line definition and its live count of approved entries. Read-only, idempotent and parameterless — call it once to learn the exact values accepted by the 'category' argument of search_registry, list_entries and discover_capabilities, and to size the catalogue before paging. It never returns entries themselves: use list_entries to enumerate a layer, search_registry for a keyword, discover_capabilities for a plain-language need.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–

No examples provided.

list_entries ~334

Enumerate the whole approved catalogue in deterministic slug order, page by page — use this when you want everything (mirroring, auditing, building your own index), not when you are looking for something specific. Read-only and idempotent. Returns {total, page, per_page, pages, results[]}: read 'pages' from the first response and increment 'page' until you reach it; 'total' and 'pages' reflect the 'category' filter when one is set, so keep the filter identical across pages or the paging shifts. Entries come back in summary form; call get_entry with a slug for the full record. For a keyword use search_registry, for a plain-language need use discover_capabilities, and for the accepted category values call list_categories. Bulk mirror alternative: GET https://agentnexus.app/api/public/entries.ndjson streams the full catalogue in one request.

NameTypeReqDescription
categorystring–Optional filter, exactly one of 'api', 'mcp' or 'cli' (see list_categories). Omit to page through all three layers. When set, 'total' and 'pages' count only that layer.
pageinteger–1-based page index. Start at 1 and increment until it equals the 'pages' value returned in the response; a page beyond the last one returns an empty results[] rather than an error.
per_pageinteger–How many entries to return in this page, 1-50, default 25. Changing it between calls changes 'pages' and re-slices the catalogue, so keep it constant while paging.
NameTypeReqDescription
pagenumberyes–
pagesnumberyes–
per_pagenumberyes–
resultsarrayyes–
totalnumberyes–

No examples provided.

search_registry ~334

Keyword lookup in the Agent Nexus registry when you already know what to look for: a product name, vendor, slug or endpoint fragment, optionally narrowed to one category. Matches literal text only — it does not interpret a goal. To go from a plain-language need to a callable interface, use discover_capabilities instead; to walk the whole catalogue in order use list_entries, and for the full record of one known slug use get_entry. Returns {count, results[]} in summary form, and an empty results[] when nothing matches — that is a valid answer, not an error.

NameTypeReqDescription
categorystring–Optional filter, exactly one of 'api', 'mcp' or 'cli' (see list_categories). Combined with query as AND. Omit to search all three layers.
limitinteger–Upper bound on entries returned, 1-50, default 10. Results are ordered by name, not by relevance, so a small limit on a broad keyword can hide better matches — raise it or use discover_capabilities w…
querystring–Literal substring, max 120 chars, matched case-insensitively against name, summary, endpoint and slug — a product name ('resend'), a vendor, a slug fragment or a host ('api.stripe.com'). Single terms…
NameTypeReqDescription
countnumberyes–
resultsarrayyes–

No examples provided.

submit_entry ~1,081

Register a new interface (HTTP API, MCP server or CLI) in the Agent Nexus catalogue. Callers authenticate either as a signed-in member or with a free agent key (POST https://agentnexus.app/api/public/keys), which allows one submission per key per 24 hours. This is a write: it creates a pending row, it does NOT publish anything — every submission is reviewed by a human before it becomes discoverable, so nothing you send here is visible to other agents until it is approved. Nothing is overwritten or deleted, and re-submitting the same name creates a second pending row rather than updating the first. Five fields are required (name, category, summary, endpoint, auth_mode); everything else is optional but directly decides whether the entry is approved and how well it ranks: capabilities[] is what other agents are matched against, so list concrete verbs, and docs_url plus invocation_example are what a reviewer checks first. Rate limited to 20 submissions per hour for members and 1 per 24 hours for agent keys, and the endpoint must answer a live health probe to keep a reliability score. Returns {slug, status}; poll GET https://agentnexus.app/api/public/submission?slug=<slug> for the decision, or pass contact_email to be emailed instead. Use list_my_submissions to review what you already submitted; use search_registry first to check the interface is not already listed.

NameTypeReqDescription
auth_modestringyesHow a caller authenticates, in a few words: 'none', 'Bearer API key', 'API key in query', 'OAuth 2.1', 'Basic auth'. Write 'none' rather than leaving it vague; auth_params carries the individual cred…
auth_paramsarray–Up to 10 individual credentials the caller must supply, each {name, location, required}. Leave empty when auth_mode is 'none'. Never include credential values here, only their names.
capabilitiesarray–Up to 12 lowercase hyphenated verbs an agent's need is matched against, e.g. ['send-email','list-templates','verify-address']. This is the single field that drives discovery: an entry with no capabil…
categorystringyesWhich layer this interface belongs to: 'api' for an HTTP contract called directly, 'mcp' for a Model Context Protocol tool server, 'cli' for a command-line surface. Decides how endpoint is interprete…
contact_emailstring–Optional. Where to email the moderation decision (approved or rejected, with the reason). Never published, never shared.
descriptionstring–Optional long form, max 4000 chars: what the interface does well, notable limits, quirks an agent should know before calling. Plain text; no HTML.
docs_urlstring–Absolute https URL of the developer documentation (not the marketing home page). Omit if none exists; submissions without it are approved more slowly.
endpointstringyesHow the interface is actually reached, max 500 chars. For category 'api' the base URL (https://api.example.com/v1); for 'mcp' the server URL (https://example.com/mcp) or stdio command; for 'cli' the…
input_formatstring–MIME type or shape the interface accepts, e.g. 'application/json', 'multipart/form-data', 'command-line flags'. Empty string when not applicable.
invocation_examplestring–One copy-pasteable call that works: a curl command, a JSON-RPC body or a CLI line, max 1000 chars. Never include a real credential — use a placeholder such as $API_KEY. This is what reviewers check f…
namestringyesPublic product name as its vendor spells it, 1-80 chars, e.g. 'Resend' or 'GitHub MCP Server'. Do not add the category or a tagline here; the slug is derived from this name plus the category.
output_formatstring–MIME type or shape the interface returns, e.g. 'application/json', 'text/csv', 'stdout text'. Empty string when not applicable.
pricingstring–Cost in one short phrase, e.g. 'Free', 'Free tier then $20/month', 'Usage-based, $0.001/call'. Agents filter on this, so be concrete.
rate_limitstring–Published quota in the vendor's own words, e.g. '100 requests/minute', '10k calls/month on the free tier'. Leave empty rather than guessing.
summarystringyesOne line an agent can rank on: what the interface does, 10-300 chars. State the capability, not the marketing (e.g. 'Send transactional email over HTTP with templates and delivery webhooks').
tagsarray–Up to 8 short domain labels for browsing, e.g. ['email','messaging']. Domains, not actions — actions belong in capabilities[].
NameTypeReqDescription
slugstringyes–
statusstringyes–

No examples provided.

Common questions

What is the Agent Nexus MCP server?

Agent Nexus is an MCP server listed in the public MCP registry as app.agentnexus/agent-nexus. 180+ tested APIs, MCP servers and CLIs your agent can call. Self-service key in one call. This page covers its hosted endpoint (https://agentnexus.app/mcp).

Is the Agent Nexus MCP server safe to use?

Agent Nexus scores 79 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 Agent Nexus MCP server expose?

Agent Nexus exposes 6 tools: discover_capabilities, search_registry, get_entry, list_categories, list_entries, submit_entry. Their descriptions and schemas cost roughly 2,460 tokens of context every time the server is loaded.

Does the Agent Nexus MCP server require authentication?

Yes. Agent Nexus asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Agent Nexus MCP server still maintained?

Agent Nexus is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.