ParseAPI
REMOTE · MCP.PARSEAPI.COM · 2 COMPONENTS
Official ParseAPI MCP. Place, IP, email, phone, weather, currency lookups.
Available components
Last scanned (19 hours ago)
Scores higher than 24% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Maps and Location
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 28 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
- 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
- 28 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.47 → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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
- 14 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Aug 26 0
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 16 Oct 2026 · Probed https://mcp.parseapi.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.parseapi.com | CN=YE1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 500cf910233c34f7977efb51d101c7be236 |
| SANs: mcp.parseapi.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 mcp.parseapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| parseapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.parseapi.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.parseapi.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| www-authenticate | Bearer resource_metadata="https://mcp.parseapi.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://mcp.parseapi.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.parseapi.com |
| Authorisation server | https://parseapi.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.parseapi.com | Auth required | 401 | |
| http (plaintext) | http://mcp.parseapi.com | HTTPS enforced | 301 | https://mcp.parseapi.com/ |
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 →
city ~87
Look up a city by name: coordinates, state, population, timezone. Pass country to disambiguate name ties.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code, e.g. US |
| name | string | yes | City name, e.g. charlotte |
| state | string | – | State code to disambiguate, e.g. NC |
No output schema declared.
No examples provided.
city_id ~45
Refetch a city by its stable parse id from an earlier response.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Stable city id, e.g. city_mb8mbqrkz8zb |
No output schema declared.
No examples provided.
city_nearest ~38
Find the nearest city to coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees |
| lon | number | yes | Longitude in decimal degrees |
No output schema declared.
No examples provided.
city_search ~78
Search cities by name prefix. Use when the exact name is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code, e.g. US |
| limit | integer | – | Max results |
| q | string | yes | Name prefix, e.g. char |
| state | string | – | State code filter |
No output schema declared.
No examples provided.
continent ~44
Look up a continent by code: name, area, population.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Continent code: AF, AN, AS, EU, NA, OC, SA |
No output schema declared.
No examples provided.
continent_countries ~40
List every country on a continent.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Continent code: AF, AN, AS, EU, NA, OC, SA |
No output schema declared.
No examples provided.
country ~49
Look up a country: names, capital, currency, languages, calling code, timezones.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
country_states ~42
List the states, provinces or regions of a country.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
currency ~40
Look up a currency: name, symbol, decimal places, countries using it.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | ISO 4217 code, e.g. USD |
No output schema declared.
No examples provided.
currency_rate ~57
Exchange rate between two currencies from official central bank data.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Base currency ISO 4217 code, e.g. USD |
| quote | string | yes | Quote currency ISO 4217 code, e.g. EUR |
No output schema declared.
No examples provided.
district ~57
Look up a district, county or department by code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | District code, e.g. 37081 |
| country | string | – | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
domain ~59
Look up a domain: registration, DNS, mail setup. Deep adds richer checks.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| domain | string | yes | Domain name, e.g. example.com |
No output schema declared.
No examples provided.
elevation ~36
Elevation in meters at coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees |
| lon | number | yes | Longitude in decimal degrees |
No output schema declared.
No examples provided.
email ~61
Validate an email address: syntax, domain, MX, disposable and role flags. Deep runs a live mailbox verification.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| string | yes | Email address to validate |
No output schema declared.
No examples provided.
emoji ~41
Look up an emoji by name or character: unicode, hex, skin tones.
| Name | Type | Req | Description |
|---|---|---|---|
| emoji | string | yes | Emoji name or the character itself, e.g. rocket |
No output schema declared.
No examples provided.
emoji_search ~36
Search emoji by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results |
| q | string | yes | Search keyword, e.g. fire |
No output schema declared.
No examples provided.
holiday ~63
Public holidays and cultural observances for a country and year. Each row carries type: public or observance.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
| year | integer | – | Year, default current |
No output schema declared.
No examples provided.
holiday_date ~65
Whether a specific date is a holiday or observance in a country. holiday is null when it is not.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
| date | string | yes | Date as YYYY-MM-DD |
No output schema declared.
No examples provided.
ip ~80
Look up an IPv4 or IPv6 address: country, region, ASN, timezone. Deep adds datacenter, relay and tor flags.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| ip | string | yes | IPv4 or IPv6 address, e.g. 8.8.8.8 |
No output schema declared.
No examples provided.
language ~49
Look up a language by BCP 47 or ISO 639-3 code: names, script, direction.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Language code, e.g. en, ja, gsw |
No output schema declared.
No examples provided.
mx ~25
MX records and mail provider for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name |
No output schema declared.
No examples provided.
phone ~92
Validate and parse a phone number: country, type, formats. Pass country for national-format numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country code for national-format numbers, e.g. US |
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| number | string | yes | Phone number, e.g. +14155552671 |
No output schema declared.
No examples provided.
point ~69
Reverse geocode coordinates to country, state, district and nearest city. Deep adds richer admin data.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| lat | number | yes | Latitude in decimal degrees |
| lon | number | yes | Longitude in decimal degrees |
No output schema declared.
No examples provided.
postal ~69
Look up a postal code: place name, coordinates, state, district, timezone, elevation. Country is required.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Postal code, e.g. 28202 |
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
postal_distance ~61
Distance between two postal codes in the same country.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
| from | string | yes | First postal code |
| to | string | yes | Second postal code |
No output schema declared.
No examples provided.
postal_nearby ~78
List postal codes near a given one, sorted by distance.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Postal code to search around |
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
| radius | number | – | Search radius |
| unit | string | – | Radius unit, default km |
No output schema declared.
No examples provided.
state ~59
Look up a state, province or region by its code within a country.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | State code, e.g. NC |
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
state_districts ~58
List the districts, counties or departments of a state.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | State code, e.g. NC |
| country | string | yes | ISO 3166-1 alpha-2 country code, e.g. US |
No output schema declared.
No examples provided.
timezone ~66
Look up an IANA timezone: current offset, DST state, local time. Pass at for a specific instant.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | ISO 8601 instant to evaluate, default now |
| timezone | string | yes | IANA timezone id, e.g. America/New_York |
No output schema declared.
No examples provided.
useragent ~56
Parse a User-Agent string: browser, OS, device, bot detection.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| ua | string | yes | The User-Agent string to parse |
No output schema declared.
No examples provided.
weather ~77
Current weather observation at coordinates from official national agencies. Every measurement ships metric and imperial side by side. Deep adds forecast and alerts where available.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Include the nested deep object with richer fields. Paid on most endpoints. |
| lat | number | yes | Latitude in decimal degrees |
| lon | number | yes | Longitude in decimal degrees |
No output schema declared.
No examples provided.
How do I install the ParseAPI MCP server?
ParseAPI is a hosted endpoint at https://mcp.parseapi.com/, 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 · mcp.parseapi.com
claude mcp add --transport http com-parseapi-mcp 'https://mcp.parseapi.com/'
What is the ParseAPI MCP server?
ParseAPI is an MCP server listed in the public MCP registry as com.parseapi/mcp. Official ParseAPI MCP. Place, IP, email, phone, weather, currency lookups. This page covers its hosted endpoint (https://mcp.parseapi.com).
Is the ParseAPI MCP server safe to use?
ParseAPI scores 36 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 ParseAPI MCP server expose?
ParseAPI exposes 31 tools: ip, continent, continent_countries, country, country_states, and 26 more. Their descriptions and schemas cost roughly 1,777 tokens of context every time the server is loaded.
Does the ParseAPI MCP server require authentication?
Yes. ParseAPI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ParseAPI MCP server still maintained?
ParseAPI is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.