_ registry / mcp + a2a http-sse · checked 1h ago

veda.ng

https://veda.ng

Registry code: 0de6a9799d08528f

api record

Tools for searching and reading the published research of Vedang Vatsa: essays on AI agents and Web3, a 100+ term glossary, and a 233,000-paper academic index. Use search_essays or search_glossary first, then get_essay or get_glossary_term for full text. Use search_reports for peer-reviewed literature. Official SDKs: JavaScript/TypeScript SDK package on NPM (npm install vedang) and Python SDK package on PyPI (pip install vedang-cli). Content is educational; it is not financial, legal, or medical advice. Full site index: https://veda.ng/llms.txt. Human-readable docs:…

endpoint
https://veda.ng/mcp
door code
eb22c95d5f7111f2
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is veda.ng live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is veda.ng free to use?
Yes — the hub reached it with no key and no payment.
What tools does veda.ng have?
6 tools: get_essay, scan_agent_readiness, search_essays, search_reports, search_glossary, get_glossary_term.
Is veda.ng safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.8%· all time 99.6%

latency
1,045ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 825 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
knowledge & reference academic & research
used for
  • search essays on ai agents and web3
  • look up an ai or web3 glossary term
  • search academic papers
  • audit a website for agent readiness
takes → gives
text → text, data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_essay reads unknown 20h ago

    Fetch the full Markdown text of one essay by its URL slug, e.g. "agentstack".

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Essay slug (the path segment after veda.ng/)."
    }
  }
}
    arguments 12 lines
  • scan_agent_readiness reads unknown 20h ago

    Audit any website for AI agent-readiness and machine discovery: evaluates robots.txt AI bot policies, llms.txt, MCP endpoints, OpenAPI schemas, and Markdown twins with a 0-100 score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Domain or URL to audit (e.g. \"stripe.com\" or \"https://example.com\")."
    }
  }
}
    arguments 12 lines
  • search_essays reads unknown 23h ago

    Search long-form essays by Vedang Vatsa on AI agents, AI policy, and Web3. Matches against titles and summaries.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Keywords to search for, e.g. \"stablecoin regulation\"."
    }
  }
}
    arguments 12 lines
  • search_reports reads unknown 23h ago

    Search 233,000+ indexed academic papers via OpenAlex in the AI or Web3 corpus, sorted by citations.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search keywords."
    },
    "corpus": {
      "enum": [
        "ai",
        "web3"
      ],
      "type": "string",
      "description": "Corpus to search (default ai)."
    },
    "per_page": {
      "type": "number",
      "description": "Results to return (1-20, default 10)."
    }
  }
}
    arguments 24 lines
  • search_glossary reads unknown 23h ago

    Search the AI & Web3 glossary (100+ terms). Returns term names, slugs, and definition previews.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Maximum number of terms to return (1-25, default 8)."
    },
    "query": {
      "type": "string",
      "description": "Keywords to search for, e.g. \"rollup\"."
    }
  }
}
    arguments 16 lines
  • get_glossary_term reads unknown 20h ago

    Fetch the full Markdown definition of one glossary term by its slug, e.g. "zk-rollup".

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Glossary term slug."
    }
  }
}
    arguments 12 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0de6a9799d08528f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0de6a9799d08528f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0de6a9799d08528f/badge.svg)](https://brick.blue/agent/0de6a9799d08528f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.