Polyform
REMOTE · API.POLYFORM.ORG · SCANNED SEP 20
Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup.
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
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 6829 tokens (~98/item across 69 items; 67 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 67 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 69 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
How do I install the Polyform MCP server?
Polyform is a hosted endpoint at https://api.polyform.org/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 · api.polyform.org
claude mcp add --transport http org-polyform-polyform 'https://api.polyform.org/mcp'
{
"mcpServers": {
"org-polyform-polyform": {
"url": "https://api.polyform.org/mcp"
}
}
} {
"servers": {
"org-polyform-polyform": {
"type": "http",
"url": "https://api.polyform.org/mcp"
}
}
} [mcp_servers.org-polyform-polyform] url = "https://api.polyform.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-polyform-polyform": {
"type": "remote",
"url": "https://api.polyform.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-polyform-polyform --url 'https://api.polyform.org/mcp' --transport streamable-http
mcp_servers:
org-polyform-polyform:
url: "https://api.polyform.org/mcp" {
"McpServers": {
"org-polyform-polyform": {
"Transport": "http",
"Url": "https://api.polyform.org/mcp"
}
}
} assistant mcp add org-polyform-polyform -t streamable-http -u 'https://api.polyform.org/mcp'
{
"mcpServers": {
"org-polyform-polyform": {
"type": "http",
"url": "https://api.polyform.org/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 15 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.
- 13 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.
- 11 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.
- 9 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.
- 7 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.
- 5 Sept 26 +1
- Schema quality: 4930 → 6829 ▼ functional
- New tool “business_onboard_decision” functional
- New tool “domain_dns_hygiene” functional
- New tool “econ_compare_countries” functional
- New tool “econ_country_snapshot” functional
- New tool “email_sender_trust” functional
- New tool “finance_diligence_brief” functional
- New tool “geo_severe_weather_scan” functional
- New tool “health_drug_safety_compare” functional
- New tool “ip_intelligence” functional
- New tool “realestate_underwrite” functional
- New tool “security_bulk_ip_screen” functional
- New tool “security_domain_threat_report” functional
- New tool “security_inbound_request_screen” functional
- New tool “security_phishing_triage” functional
- New tool “security_threat_lookup” functional
- New tool “trade_shipment_clearance” functional
- New tool “url_safety” functional
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 20 Sept 2026 · Probed https://api.polyform.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=polyform.org | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 87d554cf36651f040ee70c4088926420 |
| SANs: polyform.org, api.polyform.org, *.api.polyform.org | ||||||
| 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 api.polyform.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| polyform.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.polyform.org/mcp | Verified | 200 | |
| http (plaintext) | http://api.polyform.org/mcp | Inconclusive | 405 |
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 →
threat_scanners ~107
Polyform observed-scanner feed — Recent IPs caught probing Polyform's honeypot paths (credential/vuln scanners) — Polyform's own first-party telemetry, not a repackaged public list. Returns up to 500 most-recent scanner IPs with first-seen. For blocklists and threat research. JSON. Price: $0.01 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | 1-500 (default 200) |
No output schema declared.
No examples provided.
time_business_days ~79
US business-days calculator — Business days between two dates (exclusive of end), skipping weekends and US federal holidays; also returns the holiday list in range. Pure computation. JSON. Price: $0.001 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | YYYY-MM-DD |
| start | string | yes | YYYY-MM-DD |
No output schema declared.
No examples provided.
trade_party_screen ~148
Trade-compliance party screen (bundle) — One premium call for import/export compliance: screens a counterparty name against the US Consolidated Screening List (OFAC + BIS + State) AND pulls recent US Federal Register actions on the commodity/topic (export controls, tariffs, rules), fused into a clear/review/hold trade verdict with flags. JSON. Price: $0.20 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | optional agency slug, e.g. bureau-of-industry-and-security |
| commodity | string | – | optional commodity or topic, e.g. 'semiconductors' |
| name | string | yes | counterparty / party name to screen |
No output schema declared.
No examples provided.
trade_shipment_clearance ~132
Shipment clearance (bundle) — One call: CLEAR/REVIEW/HOLD export/import pre-screen — screens the counterparty (US CSL), checks the destination against US embargo lists, and flags export-controlled commodities. Price: $0.45 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | yes | commodity or topic for export-control check |
| country | string | yes | destination country |
| destination | string | yes | destination country (alias of country) |
| name | string | yes | counterparty/party name to screen |
| party | string | yes | counterparty name (alias of name) |
No output schema declared.
No examples provided.
url_check ~75
URL status & redirect check — HTTP status, final URL after redirects, content-type and key response headers for a URL — without downloading the body. For link vetting and uptime checks. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | http(s) URL to check |
No output schema declared.
No examples provided.
url_safety ~81
URL / link safety check (bundle) — One call: SAFE/CAUTION/DANGER verdict for a URL — checks reachability & redirects, destination domain age, and hosting-IP reputation before an agent follows the link. Price: $0.05 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | http(s) URL to check |
No output schema declared.
No examples provided.
vehicle_deal_check ~97
Used-car deal check verdict — Given vin, asking price and miles: decoded specs, open recall count, fuel-cost estimate, and a buy/caution/walk verdict with reasoning. All public federal data. Price: $0.25 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| miles | string | yes | odometer miles |
| price | string | yes | asking price USD |
| vin | string | yes | 17-char VIN |
No output schema declared.
No examples provided.
vehicle_fuel_economy ~85
Fuel economy lookup (EPA) — EPA MPG figures and estimated annual fuel cost for a year/make/model. Source: fueleconomy.gov. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| make | string | yes | manufacturer |
| model | string | yes | model name |
| year | string | yes | model year |
No output schema declared.
No examples provided.
vehicle_report ~109
Vehicle full report (bundle) — One call: decoded VIN specs + all open safety recalls + EPA fuel economy & annual cost + a buy/caution/walk verdict with reasoning. Fuses multiple NHTSA & EPA sources. JSON. Price: $0.25 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| miles | string | – | odometer miles (optional) |
| price | string | – | asking price USD (optional, enables verdict) |
| vin | string | yes | 17-char VIN |
No output schema declared.
No examples provided.
vehicle_vin ~88
VIN decode + open recalls (NHTSA) — Decode any US-market VIN to full vehicle specs and list open safety recalls. Source: US NHTSA (federal, authoritative). JSON. Price: $0.005 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| vin | string | yes | 17-character VIN, e.g. 1HGCM82633A004352 |
No output schema declared.
No examples provided.
weather_alerts ~103
Active US weather alerts (NWS) — Active watches/warnings/advisories for a US state or coordinate: event type, severity, headline, timing. Source: National Weather Service. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | string | – | optional latitude |
| lon | string | – | optional longitude |
| state | string | yes | 2-letter state e.g. TN (or use lat+lon) |
No output schema declared.
No examples provided.
weather_current ~78
US current conditions (NWS) — Latest observed conditions near a US coordinate: temperature, wind, humidity, visibility, pressure from the nearest weather station. Source: National Weather Service. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | string | yes | latitude |
| lon | string | yes | longitude |
No output schema declared.
No examples provided.
weather_forecast ~90
US weather forecast (NWS) — 7-day forecast for any US coordinate: periods with temperature, wind, precipitation chance, narrative. Source: National Weather Service. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | string | yes | latitude e.g. 36.16 |
| lon | string | yes | longitude e.g. -86.78 |
No output schema declared.
No examples provided.
weather_hourly ~95
US hourly forecast (NWS) — Hour-by-hour forecast for any US coordinate: temperature, precipitation chance, wind, conditions for the next 48 hours. Source: National Weather Service. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| hours | string | – | 1-48 (default 24) |
| lat | string | yes | latitude |
| lon | string | yes | longitude |
No output schema declared.
No examples provided.
weather_metar ~90
Aviation weather METAR/TAF (NOAA) — Raw and decoded METAR (and optional TAF) for any airport ICAO code. Source: NOAA Aviation Weather Center. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| station | string | yes | ICAO code e.g. KBNA |
| taf | string | yes | true to include TAF |
No output schema declared.
No examples provided.
weather_travel_risk ~105
US weather travel-risk verdict — Judgment call for a US coordinate and date (within 7 days): LOW/MODERATE/HIGH/SEVERE weather risk with reasons, built from NWS forecast plus active alerts. JSON. Price: $0.015 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD within 7 days (default today) |
| lat | string | yes | latitude |
| lon | string | yes | longitude |
No output schema declared.
No examples provided.
wiki_summary ~61
Wikipedia summary — Concise summary/extract for any Wikipedia topic, with the canonical URL. Source: Wikimedia REST API. JSON. Price: $0.003 USDC (Base, via x402).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | article title or search term |
No output schema declared.
No examples provided.
What is the Polyform MCP server?
Polyform is an MCP server listed in the public MCP registry as org.polyform/polyform. Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup. This page covers its hosted endpoint (https://api.polyform.org/mcp).
Is the Polyform MCP server safe to use?
Polyform 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 Polyform MCP server expose?
Polyform exposes 67 tools: vehicle_vin, vehicle_deal_check, vehicle_fuel_economy, domain, email_domain_check, and 62 more. Their descriptions and schemas cost roughly 6,740 tokens of context every time the server is loaded.
Does the Polyform MCP server require authentication?
No. We connected to Polyform without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Polyform MCP server still maintained?
Polyform is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.