AgentsIndex
REMOTE · AGENTSINDEX.AI
The editors' index of AI-native software, from AI agents to the models and frameworks behind them.
Available components
Last scanned (8 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2007 tokens (~167/item across 12 items; 12 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 Management56
- Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 52 to 56.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 46 to 49.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “submit_listing” rewrote its description, which is the text the model reads security
- 1 Nov 26 +1
- Tool “my_listings” rewrote its description, which is the text the model reads security
- 31 Oct 26 0
- Tool “my_listings” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 32 to 36.
- 27 Oct 26 +1
- Tool “subscribe_newsletter” rewrote its description, which is the text the model reads security
- 26 Oct 26 0
- Tool “create_order” rewrote its description, which is the text the model reads security
- Tool “list_offers” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://agentsindex.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentsindex.ai | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68bc0cca320f10c07e481e581fe7a6d339e |
| SANs: *.agentsindex.ai, agentsindex.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of agentsindex.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| agentsindex.ai. | present | 2371 | 13 | Verified |
| agentsindex.ai. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentsindex.ai/mcp | Verified | 200 | |
| http (plaintext) | http://agentsindex.ai/mcp | HTTPS enforced | 301 | https://agentsindex.ai/mcp |
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 →
compare_listings Compare two listings ~58
Two tools side by side, as markdown: taglines, pricing, API availability, tags — the researched compare facts, honest about unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First listing slug. |
| b | string | yes | Second listing slug. |
No output schema declared.
No examples provided.
create_order Order an offer ~177
Turns a quote (from get_quote) into an order, payable for 24 hours. Same account as the quote: its session Cookie header, or its agent key as Authorization: Bearer (order scope). Returns the order with payment.url: POST it without a credential for a 402 card challenge (MPP, method stripe, a Stripe Shared Payment Token), then again with Authorization: Payment. Pass idempotency_key to make a retry return the same order. The price is excl. VAT: EU buyers without a valid EU VAT ID pay 21% VAT on top, and the 402 shows the total. Nothing is charged by this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Optional: your own key, the same on every retry of this order. |
| quote_id | string | yes | The quote_id from get_quote. |
No output schema declared.
No examples provided.
get_best_of Best of a category ~73
The Published tools in one category, in the order its category page prints (ranked by what we can confirm: a public price, an API and docs, independent sources, stated limits), as a markdown answer sheet. Payment never moves a row.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The category slug (from list_categories). |
No output schema declared.
No examples provided.
get_listing Get one listing ~77
One tool in full, as answer-first markdown: the summary, then every question on the sheet with its answer, the vendor's own words for it and the URL that proves it. Identical to /{slug}.md and to the HTML page.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug (from search_listings or the URL). |
No output schema declared.
No examples provided.
get_quote Get a quote ~158
A signed price for one offer (from list_offers) on one listing, valid for a short time, and whether the listing can have it now. Only the account that owns the listing gets one: send its session Cookie header, or its agent key as Authorization: Bearer, on the MCP request. Refusals say why and what to do (httpStatus 401 sign_in_required, 403 not_owner with the claim page, 409 not_accepted, already_live, already_bought, category_full). Nothing is reserved or charged.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | The listing id or slug (from search_listings or get_listing). |
| offer | string | yes | An offer id from list_offers, e.g. boost. |
No output schema declared.
No examples provided.
list_categories List categories ~26
AgentsIndex's categories with their live listing counts, 0 for one with none yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_offers List paid offers ~68
What a listing owner can buy on AgentsIndex, with prices in US cents excl. VAT, each offer's term and what it needs. Keyless. Same answer as GET https://agentsindex.ai/api/agent/catalogue. Listing on AgentsIndex is free and never sold: submit_listing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_listings Read your listings ~197
What the AgentsIndex owner dashboard shows about the listings an account owns: each one's status (`status.kind`: review with the expected date, accepted with `liveOn` and `paid` ('express' | 'featured' | null: the paid way that releases it, Featured including VIP listing), live, refused with the reason, or archived), the listing as it shows, 30 days of real numbers with the 30 before, where AI answers named the product or cited its page, and what it can buy here at this site's prices. Only for the account itself: send its session Cookie header, or its agent key with "Read your listings" as Authorization: Bearer. Same answer as GET https://agentsindex.ai/api/owner/listings. Read-only: corrections go through the dashboard's request form.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Optional: one listing, by its slug. Without it, every listing the account owns. |
No output schema declared.
No examples provided.
search_listings Search listings ~65
Full-text search over AgentsIndex's Published tools. Returns compact records (name, slug, tagline, url). Fetch depth with get_listing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, cap 25). |
| query | string | yes | What to search for. |
No output schema declared.
No examples provided.
send_lead Send a lead ~204
Send a buyer-intent enquiry (lead) to a tool or a whole category on AgentsIndex. Keyless. Requires consent:true, a real name, a permanent (non-disposable) email, a message of at least 20 chars, and a target (listingSlug OR categorySlug). Returns { ok, delivered }. Idempotent by (email, target) within 7 days. Nothing here changes a listing's rank, tier or copy.
| Name | Type | Req | Description |
|---|---|---|---|
| categorySlug | string | – | Target category slug (this OR listingSlug). |
| company | string | – | Optional company name. |
| consent | boolean | yes | Must be true — you agree your details go to the provider(s). |
| string | yes | A permanent contact email (non-disposable). | |
| listingSlug | string | – | Target listing slug (this OR categorySlug). |
| message | string | yes | The enquiry — real demand, at least 20 chars. |
| name | string | yes | Your name. |
No output schema declared.
No examples provided.
submit_listing Submit a listing ~534
Submit a tool to AgentsIndex: the url alone; we write its name and description from its own pages. Requires an existing signed-in account with verified email; send its session Cookie header on the MCP request, or an agent key the account made at https://agentsindex.ai/dashboard/agents as Authorization: Bearer. Identity and email come only from that session or key. Sign in or explicitly create an account at https://agentsindex.ai/login?next=%2Fsubmit and verify its email before retrying. This tool creates no account and sends no verification email. Returns {httpStatus:201, id, slug, status:'Draft'}; research + the quality gate decide publication. Your own (url, session email) replay within 24h returns httpStatus:200. The fit check starts at once and usually answers within a minute: poll GET https://agentsindex.ai/api/submissions/{id} and wait the Retry-After seconds it sends while fit is "checking". fit then reads "accepted" (it goes live, and the account is mailed), "rejected" (mailed with the reason) or "undecided" (a person looks within 2 days). No session: {httpStatus:401, error:'sign_in_required', message, loginUrl}. Unverified session: {httpStatus:403, error:'email_unverified', message, email, remediation}. The owner must prove the site before anything is listed: the account's address, or an address it proved with a code, must be on the submitted website's domain. Otherwise the answer is the pending state {httpStatus:403, error:'domain_unverified', status:'awaiting_owner_proof', listed:false, message, domain, proveWith, ownerUrl, ownerStep, remediation}: nothing is listed or queued. proveWith names who can receive the 6-digit code (any address at the domain; for a GitHub or other shared-host project, its listed addresses or a one-line file). Submitting for someone else? Give the owner ownerUrl (the submit page with the site filled in): they enter the code there and the listing goes in once proven. With a mailbox at the domain yourself: POST /api/domain-proof/s…
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website being submitted (https). |
No output schema declared.
No examples provided.
subscribe_newsletter Subscribe to the digest ~81
Subscribe an email to the AgentsIndex digest of new and freshly re-verified tools. Provide an email; returns { ok }. The address is on the list at once and gets one welcome mail. Every mail carries a one-click unsubscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email to subscribe. | |
| source | string | – | Optional: where the subscribe came from. |
No output schema declared.
No examples provided.
How do I install the AgentsIndex MCP server?
AgentsIndex is a hosted endpoint at https://agentsindex.ai/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 · agentsindex.ai
claude mcp add --transport http ai-agentsindex-mcp 'https://agentsindex.ai/mcp'
What is the AgentsIndex MCP server?
AgentsIndex is an MCP server listed in the public MCP registry as ai.agentsindex/mcp. The editors' index of AI-native software, from AI agents to the models and frameworks behind them. This page covers its hosted endpoint (https://agentsindex.ai/mcp).
Is the AgentsIndex MCP server safe to use?
AgentsIndex scores 81 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 AgentsIndex MCP server expose?
AgentsIndex exposes 12 tools: search_listings, get_listing, list_categories, compare_listings, get_best_of, and 7 more. Their descriptions and schemas cost roughly 1,718 tokens of context every time the server is loaded.
Does the AgentsIndex MCP server require authentication?
No. We connected to AgentsIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentsIndex MCP server still maintained?
AgentsIndex is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.