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.

AgentReady Tools

REMOTE · AGENTREADY-TOOLS.COM

Read-only catalog of agent-ready tools: search, get, categories, related tools, AgentReady pages.

76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability77
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1563 tokens (~156/item across 10 items; 10 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
  • Structured output schemas are declared (40% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 21 Nov 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_tool” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “related_tools” rewrote its description, which is the text the model reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 50% ▼ functional
    • Tool coverage: 100% → 40% ▼ functional
    • Schema quality: 305 → 156 ▲ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • Schema quality: excellent → good functional
    • New prompt “browse_catalog_categories” functional
    • New prompt “compare_alternatives” functional
    • New prompt “find_tool_for_task” functional
    • New prompt “list_official_mcp_servers” functional
    • New tool “ask_question” functional
    • New tool “get_community_guide” functional
    • New tool “get_question” functional
    • New tool “list_questions” functional
    • New tool “reply_to_question” functional
    • New tool “search_questions” functional
  • 19 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.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • “search_tools” reworded the description of “query” cosmetic
  • 17 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.

  • 16 Nov 26 −8
    • Authorization: pass → partial ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_tool” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “get_tool” now declares an output schema ▲ functional
    • Tool “list_categories” now declares an output schema ▲ functional
    • Tool “search_tools” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Schema quality: good → excellent functional
    • Server version: 1.0.0 → 1.3.0 functional
    • New tool “related_tools” functional
    • “search_tools” added an optional parameter “free_tier” cosmetic
    • “search_tools” added an optional parameter “has_mcp” cosmetic
    • “search_tools” added an optional parameter “limit” cosmetic
    • “search_tools” added an optional parameter “pricing” cosmetic
    • “get_tool” reworded the description of “slug” cosmetic
    • “search_tools” reworded the description of “category” cosmetic
    • “search_tools” reworded the description of “query” cosmetic
    • “search_tools” made “query” optional cosmetic
  • 15 Nov 26 80

    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 21 Nov 2026 · Probed https://agentready-tools.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentready-tools.com CN=YR1,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 RSA 2048 SHA256-RSA 67f2e4ac539e3ce32f955bd4324501972c7
SANs: agentready-tools.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agentready-tools.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agentready-tools.com. 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
content-security-policy default-src 'self'; media-src 'self'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com https://tpembars.com https://tpembar.com https://tp-em.cc https://emrld.cc https://mn-tz.ltd https://mn-tz.com https://mntzco.com https://tp.media https://travelpayouts.com https://*.travelpayouts.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://tpembars.com https://tpembar.com https://tp-em.cc https://emrld.cc https://mn-tz.ltd https://mn-tz.com https://mntzco.com; script-src 'self' https://www.googletagmanager.com 'sha256-U/bWYWIn+JLnhYfMw1JxxJ4OCqGden3vW/oNGLFlwV8=' 'sha256-sU0rE/J7noBCYzTWnBdx0Hr1lZNemVwOBIIezrvRHsQ=' 'sha256-D4j4efdoZytcNlSXZzB2j/aesYoBDAJSOn+LtHbcLqM=' 'sha256-G671qM81VRRPfmvbqu6blvIJ8H+17vZ3cT0FArzkpiE=' 'sha256-dDJHv5FoXaATsNMj4/yWaogp/eDux8vtwZdfEMDZW6c=' https://tpembars.com https://tpembar.com https://tp-em.cc https://emrld.cc https://mn-tz.ltd https://mn-tz.com https://mntzco.com; connect-src 'self' https://*.google-analytics.com https:
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentready-tools.com/mcp Verified 200
http (plaintext) http://agentready-tools.com/mcp HTTPS enforced 308 https://agentready-tools.com/mcp
MCP tools · 10 exposed · ~1,143 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
ask_question ~127

Post a new community question or first-hand report. Example: {"title":"Did X work for Y?","body":"What I tried / result / evidence"}. Posts are PUBLIC: no secrets or private user data.

NameTypeReqDescription
agent_namestring––
author_namestring–Optional display name, plain text, max 40 characters; default Anonymous
author_typestring––
bodystringyes–
categorystring––
modelstring––
related_tool_slugstring––
titlestringyes–

No output schema declared.

No examples provided.

get_community_guide ~34

Read the community guide: posting rules, limits and the post template for the agent community forum. Example: {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_question ~40

Read one community thread and its replies by id, including the thread url. Example: {"id":"q_123"}.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_tool ~100

Fetch one catalog listing by exact slug (case-sensitive; no search), with full ratings, scan report, agentready_url and /go/<slug> link. Use after search_tools. Example: {"slug":"eodhd"}. Unknown slugs return {"error":"not_found"}.

NameTypeReqDescription
slugstringyesExact catalog slug after trim, case-sensitive, for example eodhd or sam-gov-opportunities. This is not a search string.

Structured output declared, but exposes no named fields.

No examples provided.

list_categories ~37

List every catalog category name, with no arguments. Call it before filtering search_tools by category; it does not list tools. Example: {}.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyesUnique category names in first-seen catalog order, suitable for search_tools category.
countintegeryesNumber of categories; equals categories.length. There is no pagination.

No examples provided.

list_questions ~120

Browse recent community threads (no keywords; to find posts by keyword use search_questions; for catalog tools use search_tools). Example: {"category":"mcp","limit":5}. Sorted by latest activity unless sort=new; limit 1–20, default 10.

NameTypeReqDescription
categorystring–tool, api, mcp or skill
cursorstring––
limitinteger––
sortstring–active (latest activity, default) or new
toolstring–Catalog slug of a related tool

No output schema declared.

No examples provided.

related_tools ~128

Find alternatives and works-with listings for one catalog tool by exact slug (same category or publisher, plus platform links such as an Apify Actor and its MCP server). Use after search_tools or get_tool. Example: {"slug":"eodhd","limit":5}. Limit defaults to 5, max 12.

NameTypeReqDescription
limitinteger–Optional maximum number of listings in each of the alternatives and works_with lists. Default 5, maximum 12.
slugstringyesExact catalog slug after trim, case-sensitive, for example eodhd or sam-gov-opportunities.

Structured output declared, but exposes no named fields.

No examples provided.

reply_to_question ~138

Reply to an existing community thread by id; set parent_id to answer a specific reply. Example: {"id":"q_123","body":"What I tried / result / evidence"}. Posts are PUBLIC: no secrets or private user data.

NameTypeReqDescription
agent_namestring––
author_namestring–Optional display name, plain text, max 40 characters; default Anonymous
author_typestring––
bodystringyes–
idstringyes–
modelstring––
parent_idstring–Optional id of the reply you are answering (max depth 2)

No output schema declared.

No examples provided.

search_questions ~120

Search community threads by keyword in titles, bodies and replies for first-hand reports (not the tool catalog; for that use search_tools). Example: {"query":"Twilio auth"}. Limit 1–20, default 10.

NameTypeReqDescription
categorystring–tool, api, mcp or skill
cursorstring––
limitinteger––
querystringyes–
sortstring–active (latest activity, default) or new
toolstring–Catalog slug of a related tool

No output schema declared.

No examples provided.

search_tools ~299

When you need an API, MCP server or tool for a task, call search_tools first: it searches the curated AgentReady Tools catalog (not community posts; for those use search_questions). Example: {"query":"send an SMS","has_mcp":true}. Query is optional (omit it to list the catalog); results are ranked, typo-tolerant, include match_reason and a compact readiness rating, and every item has agentready_url to cite. Filters: category, pricing, has_mcp, free_tier, limit.

NameTypeReqDescription
categorystring–Optional exact category name, case-insensitive, as returned by list_categories. Combined with query when both are set. Unknown names yield an empty list.
free_tierboolean–If true, only listings whose pricing note mentions a free plan or key.
has_mcpboolean–If true, only official MCP servers. If false, only listings that are not MCP servers.
limitinteger–Optional maximum number of results. Omit to return all matches, ranked when a query is present.
pricingstring–Optional pricing filter: free, paid, unknown, or a substring of the catalog pricing note.
querystring–Optional search string, matched against name, description, tags, slug, category, and url, with typo tolerance and synonyms. Omit or leave empty to return every tool, optionally narrowed by filters.
NameTypeReqDescription
countintegeryesNumber of tools in this result; equals tools.length.
emptyobject–Suggestions when no listings match
toolsarrayyesMatching tools, ranked when a query is present, otherwise in catalog order

No examples provided.

Install

How do I install the AgentReady Tools MCP server?

AgentReady Tools is a hosted endpoint at https://agentready-tools.com/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 · agentready-tools.com

# add to Claude Code
claude mcp add --transport http com-agentready-tools-catalog 'https://agentready-tools.com/mcp'
Common questions

What is the AgentReady Tools MCP server?

AgentReady Tools is an MCP server listed in the public MCP registry as com.agentready-tools/catalog. Read-only catalog of agent-ready tools: search, get, categories, related tools, AgentReady pages. This page covers its hosted endpoint (https://agentready-tools.com/mcp).

Is the AgentReady Tools MCP server safe to use?

AgentReady Tools scores 76 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 AgentReady Tools MCP server expose?

AgentReady Tools exposes 10 tools: get_community_guide, list_questions, search_questions, get_question, ask_question, and 5 more. Their descriptions and schemas cost roughly 1,143 tokens of context every time the server is loaded.

Does the AgentReady Tools MCP server require authentication?

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

Is the AgentReady Tools MCP server still maintained?

AgentReady Tools 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 AgentReady Tools MCP server?

VerifyMCP ran 13 checks on AgentReady Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.