progrss
REMOTE · PROGRSS.COM
Sourced charts on how the world is shifting: power, economy, energy, people, planet, food.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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. 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 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 503 tokens (~83/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
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 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.
- 4 Nov 26 +1
- Tool “get_plate” rewrote its description, which is the text the model reads security
- Schema quality: 70 → 83 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_numbers” functional
- 3 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 5 Nov 2026 · Probed https://progrss.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=progrss.com | CN=YE2,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5656066b7f34cf69bd841e592dd5f81e968 |
| SANs: *.progrss.com, progrss.com | ||||||
| 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 insecure
Validation of progrss.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| progrss.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 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; frame-src 'self'; connect-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://progrss.com/mcp | Verified | 200 | |
| http (plaintext) | http://progrss.com/mcp | HTTPS enforced | 301 | https://progrss.com/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_numbers Get the sourced numbers ~152
The verified numbers behind progrss plates, one per row: country or group, indicator, unit, period, value, claim type (Fact / Estimate / Forecast), and the original publisher, report, edition and link. Search by keywords (e.g. "Nigeria population", "cobalt", "USGS") and/or a plate number. Every number was read on the primary publisher's own page; cite the publisher and the plate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| plate | string | – | Optional plate number, e.g. "037", to get all its numbers. |
| query | string | – | Keywords: a country (name or ISO code), an indicator, a publisher. Every keyword must match. |
No output schema declared.
No examples provided.
get_plate Get one plate ~71
One plate in full: title, subtitle, three takeaways, the data table, the original source with link and data year, claim types (Fact / Estimate / Interpretation / Forecast), the image link, and the credit line to use.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Plate number, e.g. "037". |
No output schema declared.
No examples provided.
get_story Get one story ~30
One story with its plates in reading order.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Story slug from list_stories. |
No output schema declared.
No examples provided.
latest_plates Latest plates ~25
The newest progrss plates, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_stories List stories ~34
progrss stories: storylines of plates in reading order, e.g. "Africa's century", "The energy switch".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_plates Search progrss plates ~116
Find progrss plates (sourced charts on how the world is shifting: power, economy, energy, technology, people, cities, planet, food, future) by keywords, e.g. "cobalt Congo", "India rice exports", "Japan births". Returns titles, URLs, sources and data years. Use get_plate for the numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Keywords: a country, a commodity, a topic. |
| territory | string | – | Optional: limit to one territory. |
No output schema declared.
No examples provided.
How do I install the progrss MCP server?
progrss is a hosted endpoint at https://progrss.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 · progrss.com
claude mcp add --transport http com-progrss-plates 'https://progrss.com/mcp'
What is the progrss MCP server?
progrss is an MCP server listed in the public MCP registry as com.progrss/plates. Sourced charts on how the world is shifting: power, economy, energy, people, planet, food. This page covers its hosted endpoint (https://progrss.com/mcp).
Is the progrss MCP server safe to use?
progrss scores 72 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 progrss MCP server expose?
progrss exposes 6 tools: search_plates, get_plate, get_numbers, latest_plates, list_stories, get_story. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Does the progrss MCP server require authentication?
No. We connected to progrss without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the progrss MCP server still maintained?
progrss 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.