Agent Charts
REMOTE · AGENTS.AGENTCHARTS.XYZ
Paid AI-agent tools ranked by real on-chain spend, wash trading filtered out. Updated daily.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
Recent critical change
Authorization (19 Nov 2026). See the changelog before you install this server.
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (finish_add). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1231 tokens (~205/item across 6 items; 6 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 Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 −7
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- New tool “finish_add”, which the server declares destructive security
- Schema quality: 172 → 205 ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “add_service” functional
- 18 Nov 26 +2
- DNSSEC: fail → pass ▲ security
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 147 → 172 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.0.1 → 1.1.0 functional
- New tool “search” functional
- 14 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.
- 12 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.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 71
First indexed and scored.
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://agents.agentcharts.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentcharts.xyz | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 1fd2eb222fe2cb180eecbb834a542318 |
| SANs: agentcharts.xyz, agents.agentcharts.xyz, *.agents.agentcharts.xyz | ||||||
| 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 secure
Validation of agents.agentcharts.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| agentcharts.xyz. | DS published | 2371 | 13 | Verified |
| agents.agentcharts.xyz. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.agentcharts.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://agents.agentcharts.xyz/mcp | HTTPS enforced | 301 | https://agents.agentcharts.xyz/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 →
add_service ~336
Start adding a tool that Agent Charts doesn't list yet to its list of sellers: an API, an MCP server or a paid endpoint that AI agents can use. Only for the owner of the tool, on a domain the owner controls, with details taken from the tool's own site. Returns a code, a private token, the entry as it will be published and the value to publish on the domain, as a file or a DNS TXT record, to prove the domain; then call finish_add. Nothing shows until finish_add succeeds and the entry has been read. The row gets the label "Added by the seller", with no rank and no numbers. A domain that is listed already returns an error with its claim link. At most 5 new services a day. Free, no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The one category that fits best |
| domain | string | yes | The tool's host, such as example.com or api.example.com. The code goes on this host; a leading www. is dropped |
| line | – | – | One line on what it does, up to 120 characters. Shown |
| link | string | yes | Where people and agents go, starting with https://. Shown |
| logo | – | – | An https:// link to a PNG, JPG or WebP of at most 512 KB, with no redirect. Shown |
| name | string | yes | The tool's name, up to 40 characters. Shown |
| pays | array | yes | Every way agents pay for it: x402, mpp, card (a card or an API key) or free |
No output schema declared.
No examples provided.
best_tools ~177
Rank the paid tools in one category by what real buyers spent on them in the last 30 days (x402 and MPP payments, wash trading filtered out). Returns every ranked seller, rank 1 first, each with spend in USD, buyers, paid calls, median price per call, chains, a link to its site and its Agent Charts page. Use it to choose a tool for a job; use seller to check one domain you already know. An unknown slug returns an error: the slugs come from categories. Read-only and free, no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | A category slug from categories, such as web-search |
| max_price | number | – | Keep only sellers whose median price per call is at most this many USD, such as 0.01. Sellers with no median price stay in |
No output schema declared.
No examples provided.
categories ~66
List every category Agent Charts ranks, each with its slug and name, such as web-search. Call this first: best_tools takes one of these slugs. Every answer carries data_as_of, the last day in the data, which updates daily. Read-only and free, no sign-in.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
finish_add ~186
Finish adding a tool to Agent Charts, after add_service and after its value is published on the tool's domain. Agent Charts looks for the value on the domain and, if it is there, files the entry: it is read and then shows at agentcharts.xyz/sellers/<domain>/, usually within the hour. Leave the file or the DNS record in place until it shows. An error that the value wasn't found, or that today's places are taken, leaves the code working: call again later with the same code and token, not in a loop. Adding a domain again replaces its earlier entry. Free, no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code add_service returned |
| – | – | The owner's contact email, only if the owner gives one. Kept private and never shown | |
| token | string | yes | The private token add_service returned with that code |
No output schema declared.
No examples provided.
search ~231
Find the ranked sellers that list something for a specific job, by words such as pdf, tweets or web search. Returns two groups, each ordered by what real buyers spent on the seller in the last 30 days: focused, the sellers with every word in at least 1 in 5 of their listed endpoints, each with that share; and mentions, the sellers that list every word somewhere. The spend is the seller's whole spend, not only for what matched, and the words are the sellers' own. Use it when no category fits the job; use best_tools to rank a whole category and seller to check one domain. Read-only and free, no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Keep only sellers in this category, a slug from categories |
| limit | integer | – | Rows in each group, 10 unless given |
| max_price | number | – | Keep only sellers whose median price per call is at most this many USD. Sellers with none stay in |
| query | string | yes | One to five words of three or more letters or digits, such as pdf or web search |
No output schema declared.
No examples provided.
seller ~134
Look up one ranked seller by its domain: its category and rank; its spend in USD, buyers and paid calls over the last 30 days; median price per call; chains; its rank, spend and buyers at the end of each recent week; a link to its site and its Agent Charts page. Use it to check a tool you already have in mind; use best_tools to compare a whole category. A domain that isn't ranked returns an error. Read-only and free, no sign-in.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The seller's domain in lowercase, without https:// or a path, such as exa.ai |
No output schema declared.
No examples provided.
How do I install the Agent Charts MCP server?
Agent Charts is a hosted endpoint at https://agents.agentcharts.xyz/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 · agents.agentcharts.xyz
claude mcp add --transport http xyz-agentcharts-ranking 'https://agents.agentcharts.xyz/mcp'
What is the Agent Charts MCP server?
Agent Charts is an MCP server listed in the public MCP registry as xyz.agentcharts/ranking. Paid AI-agent tools ranked by real on-chain spend, wash trading filtered out. Updated daily. This page covers its hosted endpoint (https://agents.agentcharts.xyz/mcp).
Is the Agent Charts MCP server safe to use?
Agent Charts scores 69 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 Agent Charts MCP server expose?
Agent Charts exposes 6 tools: categories, best_tools, seller, search, add_service, finish_add. Their descriptions and schemas cost roughly 1,130 tokens of context every time the server is loaded.
Does the Agent Charts MCP server require authentication?
No. We connected to Agent Charts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Charts MCP server still maintained?
Agent Charts 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 Agent Charts MCP server?
VerifyMCP ran 13 checks on Agent Charts, 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.