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.

a9n9 Deep Research

REMOTE · AGENT.A9N9.NET · SCANNED OCT 4

Objective-driven deep research: free daily quick search plus MPP-paid cross-source browser reports.

Available components

0 this week 77 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 Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 946 tokens (~189/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
  • Structured output schemas are declared (80% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the a9n9 Deep Research MCP server?

a9n9 Deep Research is a hosted endpoint at https://agent.a9n9.net/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 · agent.a9n9.net

# add to Claude Code
claude mcp add --transport http net-a9n9-deep-research 'https://agent.a9n9.net/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "net-a9n9-deep-research": {
      "url": "https://agent.a9n9.net/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "net-a9n9-deep-research": {
      "type": "http",
      "url": "https://agent.a9n9.net/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.net-a9n9-deep-research]
url = "https://agent.a9n9.net/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-a9n9-deep-research": {
      "type": "remote",
      "url": "https://agent.a9n9.net/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add net-a9n9-deep-research --url 'https://agent.a9n9.net/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  net-a9n9-deep-research:
    url: "https://agent.a9n9.net/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "net-a9n9-deep-research": {
      "Transport": "http",
      "Url": "https://agent.a9n9.net/mcp"
    }
  }
}
# add to Vellum
assistant mcp add net-a9n9-deep-research -t streamable-http -u 'https://agent.a9n9.net/mcp'
// mcp.json
{
  "mcpServers": {
    "net-a9n9-deep-research": {
      "type": "http",
      "url": "https://agent.a9n9.net/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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

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 4 Oct 2026 · Probed https://agent.a9n9.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a9n9.net CN=WE1,O=Google Trust Services,C=US 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 e8943ccfbecd11be13c0e1372faf579a
SANs: a9n9.net, agent.a9n9.net, *.agent.a9n9.net
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 agent.a9n9.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
a9n9.net. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agent.a9n9.net/mcp Verified 200
http (plaintext) http://agent.a9n9.net/mcp Inconclusive 405
MCP tools · 5 exposed · ~829 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
a9n9_quick_search ~137

Free first-level search, limited per day across all callers: current news coverage (100+ languages, 250K+ sources) or scholarly papers (arXiv). Returns structured results immediately with no payment. When the daily quota is exhausted, or when you need live browsing and synthesis across sources, use a9n9_research_quote for paid deep research.

NameTypeReqDescription
domainstring–news (default): global news articles. papers: arXiv preprints.
payer_addressstring–Optional Tempo payer address so free usage counts toward loyalty pricing on paid research.
querystringyes–

No output schema declared.

No examples provided.

a9n9_research_quote ~224

Analyze a deep-research objective and return the exact current price, limits, planned start URLs, request hash, expiry, payment requirements, and cloud-browser capabilities without charging or starting a job. targetUrl is optional: omit it and the quote derives and binds a bounded plan of public start URLs from the objective.

NameTypeReqDescription
job_keystringyesjob_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical req…
objectivestringyes–
payer_addressstring–Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.
targetUrlstring–Optional public HTTPS focus hint; when omitted the service plans up to 5 public start URLs from the objective and binds them into the quote.
NameTypeReqDescription
chainId–yes–
cloudBrowserobjectyes–
currency–yes–
expiresAtstringyes–
limitsobjectyes–
network–yes–
nextStepstringyes–
paymentobjectyes–
paymentChallengeobjectyes–
pricestringyes–
quoteIdstringyes–
rationalestring––
requestBodyHashstringyes–
tier–yes–
walletPaymentobjectyes–

No examples provided.

a9n9_research_start ~300

Start bounded paid research in a real remotely hosted Browserbase Chromium session with JavaScript rendering, DOM interaction, scrolling, and dynamic-content extraction, followed by gpt-5.6-luna synthesis. targetUrl is optional; without it the quoted plan of public start URLs derived from the objective is executed. Call a9n9_research_quote first when price visibility is needed. The service does not bypass CAPTCHAs, logins, paywalls, access controls, or site terms.

NameTypeReqDescription
job_keystringyesjob_key identifies a research session. Reuse it with a new objective to run a follow-up iteration that references the session's prior results (each iteration is a separate paid job); an identical req…
notify_emailstring–Optional: email the completed report to this address from a9n9@agentmail.to. Delivery preference only; not part of the payment-bound request hash.
objectivestringyes–
payer_addressstring–Optional Tempo payer address for loyalty pricing: 10% off after $2.00 of reconciliation-confirmed on-chain spend from that address. Settlement must then come from it.
targetUrlstring–Optional public HTTPS focus hint; when omitted the service plans up to 5 public start URLs from the objective and binds them into the quote.
NameTypeReqDescription
createdAtstring––
errorstring––
progressPercentintegeryes–
progressStagestringyes–
quoteIdstring––
requestBodyHashstring––
resultobject––
status–yes–
statusUrlstring––
trackerCodestringyes–

No examples provided.

a9n9_research_status ~34

Return milestone progress and the final result for an opaque tracker code.

NameTypeReqDescription
trackerCodestringyes–
NameTypeReqDescription
createdAtstring––
errorstring––
progressPercentintegeryes–
progressStagestringyes–
quoteIdstring––
requestBodyHashstring––
resultobject––
status–yes–
statusUrlstring––
trackerCodestringyes–

No examples provided.

a9n9_research_submit_payment ~134

Verify a separately broadcast Tempo mainnet push-mode payment and continue the quoted research job. Use the paymentChallenge and walletPayment returned by a9n9_research_quote, then provide the transaction hash, payer address, and same job_key.

NameTypeReqDescription
job_keystringyes–
notify_emailstring–Optional: email the completed report to this address from a9n9@agentmail.to.
payer_addressstringyes–
payment_challengeobjectyesUnmodified paymentChallenge returned by a9n9_research_quote.
transaction_hashstringyes–
NameTypeReqDescription
createdAtstring––
errorstring––
progressPercentintegeryes–
progressStagestringyes–
quoteIdstring––
requestBodyHashstring––
resultobject––
status–yes–
statusUrlstring––
trackerCodestringyes–

No examples provided.

Common questions

What is the a9n9 Deep Research MCP server?

a9n9 Deep Research is an MCP server listed in the public MCP registry as net.a9n9/deep-research. Objective-driven deep research: free daily quick search plus MPP-paid cross-source browser reports. This page covers its hosted endpoint (https://agent.a9n9.net/mcp).

Is the a9n9 Deep Research MCP server safe to use?

a9n9 Deep Research scores 77 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 a9n9 Deep Research MCP server expose?

a9n9 Deep Research exposes 5 tools: a9n9_quick_search, a9n9_research_quote, a9n9_research_start, a9n9_research_submit_payment, a9n9_research_status. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.

Does the a9n9 Deep Research MCP server require authentication?

No. We connected to a9n9 Deep Research without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the a9n9 Deep Research MCP server still maintained?

a9n9 Deep Research is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.