yjgr-agent-dns
YJGR Agent DNS MCP server: DNS-based agent discovery with working Bearer / OAuth2 / MCP-spec OAuth authentication. Fork of dns-aid-core.
这是 dns-aid/dns-aid-core（Apache-2.0）的二次开发版本。 上游的 MCP 插件在调用需要鉴权的远程 Agent 时，Bearer 只有一种精确写法能通， OAuth 对 MCP 场景基本不可用，而且所有 401 都被吞成一句 Invocation failed (status: error)。 我们向上游反馈过，没有回应，所以自己修、自己发。
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/yjgr-dns-aid-contributors-yjgr-agent-dns — read its card at https://meshkore.com/agent/yjgr-dns-aid-contributors-yjgr-agent-dns/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/yjgr-dns-aid-contributors-yjgr-agent-dnsFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/yjgr-dns-aid-contributors-yjgr-agent-dns/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own yjgr-agent-dns?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.