ChartAnt
REMOTE · CHARTANT.NET
Charts, diagrams and maps of every country as PNG links for AI assistants. Free, no key, EU-hosted.
Available components
Last scanned (12 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
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 Security63
- 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 (manage_workspace). See how to fix → View diagnostics → Fail
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 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 14254 tokens (~274/item across 52 items; 51 tools + 1 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 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 53 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 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 0
- Stability: unverified → 0.03 ▲ functional
- 15 Nov 26 67
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://chartant.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.chartant.net | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 5749608c3364065f11d745102e7fff27adf |
| SANs: *.chartant.net, chartant.net | ||||||
| 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 chartant.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| chartant.net. | 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=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chartant.net/mcp | Verified | 200 | |
| http (plaintext) | http://chartant.net/mcp | HTTPS enforced | 301 | https://chartant.net/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 →
manage_workspace Manage workspace ~205
Team and sharing settings of the connected workspace. operation: list_team; invite_member (args {email}) and remove_member (args {member: user id from list_team}) for the owner only; list_client_pages, create_client_page (args {name, charts: [chart ids]}) and delete_client_page (args {id}) for read-only pages to share with clients; list_domains, add_domain (args {host, page: client page id}), verify_domain and remove_domain (args {host}) for a custom domain (Team or Business owner). remove_member, delete_client_page and remove_domain cannot be undone. Returns the result as JSON. Needs a connection signed in to a free account (connector URL ending in /mcp/account).
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | Arguments for the operation, e.g. {"email":"ana@example.com"}; {} for list operations. |
| operation | string | yes | What to do; see the description for each operation's args. |
No output schema declared.
No examples provided.
match_places Clean up place names ~215
Turn messy place names into standard names and codes: countries (ISO 3166 codes), the states/provinces/regions of one country (ISO 3166-2 codes) or US counties (FIPS codes). Understands other languages, abbreviations and typos ("Bayern", "BY", "Bavarai" → Bavaria, DE-BY). Use it to clean a column of locations before a map, a join or a report. Draws nothing; returns one line per name: the standard name and code, the options when ambiguous, or 'not found' with a suggestion.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | For regions: the country, e.g. 'DE' or 'Germany'. |
| level | string | – | country (default without 'country'), region (needs 'country') or county (US). |
| names | array | yes | The place names to clean, as written in the data. |
| state | string | – | For US counties: limit to one state, e.g. 'TX'. |
No output schema declared.
No examples provided.
restore_chart_version Restore chart version ~104
Make an earlier version of a living chart the current one again (the version in between stays in the history, so this can be undone). Its link shows the restored version and attached destinations get a fresh copy. Needs a connection signed in to a free account (connector URL ending in /mcp/account).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The chart id from create_living_chart or list_my_charts. |
| version | integer | yes | The version number from list_chart_versions. |
No output schema declared.
No examples provided.
schedule_chart Schedule chart delivery ~196
Post a living chart to a destination at a fixed time, daily or weekly (e.g. every Monday at 08:00 UTC), with its latest data. Calling it again for the same chart and destination replaces the schedule. To send whenever the data changes use send_chart_on_update. Returns a confirmation. Needs a connection signed in to a free account (connector URL ending in /mcp/account).
| Name | Type | Req | Description |
|---|---|---|---|
| destination_id | integer | yes | The destination id from add_destination or list_my_charts. |
| frequency | string | yes | daily or weekly. |
| hour | integer | – | Hour of the day in UTC (default 8). |
| id | string | yes | The chart id from create_living_chart or list_my_charts. |
| on_update | boolean | – | Also send whenever the data changes. |
| weekday | integer | – | For weekly: 0 = Sunday, 1 = Monday (default) … 6 = Saturday. |
No output schema declared.
No examples provided.
send_chart_on_update Send a chart whenever it changes ~130
Post a living chart to a destination every time its data changes (through update_living_chart or the API), and by default once right now. For a fixed daily or weekly time use schedule_chart instead. Returns a confirmation. Needs a connection signed in to a free account (connector URL ending in /mcp/account).
| Name | Type | Req | Description |
|---|---|---|---|
| chart_id | string | yes | The chart id from create_living_chart or list_my_charts. |
| destination_id | integer | yes | The destination id from add_destination or list_my_charts. |
| send_now | boolean | – | Also send it once now (default true). |
No output schema declared.
No examples provided.
update_living_chart Update a chart's data ~203
Replace the data (or the whole chart) of a chart made with create_living_chart. Its link stays the same, pages showing it update, and destinations attached to it with send_chart_on_update get a fresh copy. Sending the same data again changes nothing and sends nothing. The previous version stays in the history (list_chart_versions, restore_chart_version). For a report, send the whole report (title and blocks) as chart. Returns a confirmation with the link. Needs a connection signed in to a free account (connector URL ending in /mcp/account).
| Name | Type | Req | Description |
|---|---|---|---|
| chart | object | – | A whole new chart definition instead of only data. |
| data | – | – | The new data rows, same format as before. |
| id | string | yes | The chart id from create_living_chart or list_my_charts. |
| name | string | – | A new name for the chart. |
| stamp | boolean | – | Draw the last-updated timestamp in the title. |
No output schema declared.
No examples provided.
How do I install the ChartAnt MCP server?
ChartAnt is a hosted endpoint at https://chartant.net/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 · chartant.net
claude mcp add --transport http net-chartant-chartant 'https://chartant.net/mcp'
What is the ChartAnt MCP server?
ChartAnt is an MCP server listed in the public MCP registry as net.chartant/chartant. Charts, diagrams and maps of every country as PNG links for AI assistants. Free, no key, EU-hosted. This page covers its hosted endpoint (https://chartant.net/mcp).
Is the ChartAnt MCP server safe to use?
ChartAnt 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 ChartAnt MCP server expose?
ChartAnt exposes 51 tools: generate_world_map, generate_country_map, generate_county_map, generate_kpi_card, generate_pin_map, and 46 more. Their descriptions and schemas cost roughly 14,112 tokens of context every time the server is loaded.
Does the ChartAnt MCP server require authentication?
No. We connected to ChartAnt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChartAnt MCP server still maintained?
ChartAnt 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 ChartAnt MCP server?
VerifyMCP ran 14 checks on ChartAnt, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.