Quantamentry
REMOTE · WWW.QUANTAMENTRY.COM · SCANNED SEP 25
Daily sovereign-credibility and macro scores for 169 emerging markets, built on free public data.
Available components
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 not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 214 tokens (~71/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Quantamentry MCP server?
Quantamentry is a hosted endpoint at https://www.quantamentry.com/api/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 · www.quantamentry.com
claude mcp add --transport http com-quantamentry-quantamentry 'https://www.quantamentry.com/api/mcp'
{
"mcpServers": {
"com-quantamentry-quantamentry": {
"url": "https://www.quantamentry.com/api/mcp"
}
}
} {
"servers": {
"com-quantamentry-quantamentry": {
"type": "http",
"url": "https://www.quantamentry.com/api/mcp"
}
}
} [mcp_servers.com-quantamentry-quantamentry] url = "https://www.quantamentry.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-quantamentry-quantamentry": {
"type": "remote",
"url": "https://www.quantamentry.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-quantamentry-quantamentry --url 'https://www.quantamentry.com/api/mcp' --transport streamable-http
mcp_servers:
com-quantamentry-quantamentry:
url: "https://www.quantamentry.com/api/mcp" {
"McpServers": {
"com-quantamentry-quantamentry": {
"Transport": "http",
"Url": "https://www.quantamentry.com/api/mcp"
}
}
} assistant mcp add com-quantamentry-quantamentry -t streamable-http -u 'https://www.quantamentry.com/api/mcp'
{
"mcpServers": {
"com-quantamentry-quantamentry": {
"type": "http",
"url": "https://www.quantamentry.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 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.
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 25 Sept 2026 · Probed https://www.quantamentry.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quantamentry.com | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d56e7d7a95acda44135637858f36d361 |
| SANs: quantamentry.com, *.quantamentry.com | ||||||
| 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 insecure
Validation of www.quantamentry.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| quantamentry.com. | absent | 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; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| 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://www.quantamentry.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.quantamentry.com/api/mcp | HTTPS enforced | 301 | https://www.quantamentry.com/api/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 →
get_country ~98
Get one country's public sovereign-credibility reading: the 0-100 composite score, its credibility band, its rank and percentile within its region, the 7-day move, a one-line read and the score date. The seven underlying dimensions, the executive summary and the 90-day history are not in the free tier.
| Name | Type | Req | Description |
|---|---|---|---|
| iso | string | yes | ISO 3166-1 alpha-3 country code, e.g. 'BRA'. |
No output schema declared.
No examples provided.
get_latest_briefing ~46
Get the current weekly briefing in full: which sovereign credibility scores moved this week, by how much, and which dimension drove each move. Published every Monday and free to read.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_countries ~70
List every country Quantamentry scores, in rank order by composite sovereign-credibility score, plus the 'monitored' countries held out of the headline ranking for thin data coverage. Free tier: credibility BAND only, no composite scores and no deltas. Call get_country for a single country's score.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Quantamentry MCP server?
Quantamentry is an MCP server listed in the public MCP registry as com.quantamentry/quantamentry. Daily sovereign-credibility and macro scores for 169 emerging markets, built on free public data. This page covers its hosted endpoint (https://www.quantamentry.com/api/mcp).
Is the Quantamentry MCP server safe to use?
Quantamentry scores 77 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 Quantamentry MCP server expose?
Quantamentry exposes 3 tools: list_countries, get_country, get_latest_briefing. Their descriptions and schemas cost roughly 214 tokens of context every time the server is loaded.
Does the Quantamentry MCP server require authentication?
No. We connected to Quantamentry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Quantamentry MCP server still maintained?
Quantamentry is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.