Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ParseAPI

NPM · PARSEAPI-MCP · 2 COMPONENTS

Official ParseAPI MCP. Place, IP, email, phone, weather, currency lookups.

−1 this week 92 Trust /100

Last scanned (1 hour ago)

Scores higher than 94% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to parseapi/mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 14066 tokens (~158/item across 89 items; 89 tools + 0 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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
  • Structured output schemas are declared (1% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bank" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 89 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 −1
    • Schema quality: 129 → 158 ▼ functional
    • Package version: 1.9.5 → 1.10.0 functional
    • Package version: 1.9.5 → 1.9.6 functional
  • 15 Oct 26 +43
    • Injection markers: unverified → pass ▲ security
    • Schema quality: 9585 → 10743 ▼ functional
    • Schema quality: 9585 → 10762 ▼ functional
    • Stability: unverified → 0.90 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.9.4 → 1.9.5 functional
    • Package version: 1.8.0 → 1.9.4 functional
  • 14 Oct 26 0
    • Injection markers: unverified → pass ▲ security
    • Schema quality: 9585 → 10754 ▼ functional
    • Stability: unverified → 0.87 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 1.9.3 → 1.9.4 functional
    • Package version: 1.8.0 → 1.9.3 functional
  • 12 Oct 26 −44
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.97 → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.8.0 → 1.9.3 functional
    • Package version: 1.8.0 → 1.9.0 functional
  • 4 Oct 26 0
    • Stability: fail → 0.97 functional
  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 94.

  • 30 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 17 Oct 2026 · Analysed npm/parseapi-mcp@1.10.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo parseapi/mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/parseapi/mcp/.github/workflows/publish.yml@refs/tags/1.10.0
Rekor log index 3275696693
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:01bff747741c35636f440c078ac4dab036c57947bdcc59eb220a7a41bc25bada1c086c02ba7aed8dd02983b8b9283be1724bd478b55d7afbdebcf51b3

Background: How many MCP packages publish verified provenance →

Dependencies 7 packages
Packages resolved 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 89 exposed · ~14,066 tokens

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 →

Tool Tokens
holiday_date ~65

Whether a specific date is a holiday or observance in a country. holiday is null when it is not.

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2 country code, e.g. US
datestringyesDate as YYYY-MM-DD

No output schema declared.

No examples provided.

iban ~114

Parse an IBAN and check its format, ISO checksum, and published national BBAN checks, with known bank identifiers. Deep adds check digits, branch and account decomposition on every plan. Does not verify an account exists.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code when the number has no prefix, e.g. US
deepboolean–Include optional detail on every plan.
ibanstringyesIBAN, with or without spaces, with or without the country prefix

No output schema declared.

No examples provided.

industry ~74

Look up a US NAICS 2022 code, title and parent hierarchy. Deep adds definition, children and exclusions on paid plans.

NameTypeReqDescription
codestringyesNAICS code, e.g. 541511 or sector range 31-33
deepboolean–Include the complete detail bag on a paid plan.

No output schema declared.

No examples provided.

industry_search ~91

Search US NAICS 2022 titles and activities. Matching text and corrections stay with the result. Deep adds definition, children and exclusions inside each result on paid plans.

NameTypeReqDescription
deepboolean–Include the complete detail bag on a paid plan.
limitinteger–Maximum results, 1-50. Default 10.
querystringyesIndustry keywords, e.g. coffee shop

No output schema declared.

No examples provided.

ip ~110

Look up an IPv4 or IPv6 address: country, region, ASN, timezone. Deep adds datacenter, relay, tor and vpn flags.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
ipstringyesIPv4 or IPv6 address, e.g. 8.8.8.8
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

ip_self ~69

Look up the public IP of the machine running this MCP server.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

language ~86

Language names, script and writing direction. Deep adds ISO3 and country associations on every plan.

NameTypeReqDescription
codestringyesLanguage code, e.g. en, ja, gsw
deepboolean–Include optional detail on every plan.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

mac ~46

Normalize a 48-bit MAC address and return its registered assignment holder, local flag, and multicast flag. Vendor is null for local or multicast addresses.

NameTypeReqDescription
macstringyesMAC address

No output schema declared.

No examples provided.

measure ~155

Parse a measurement or convert it to a target unit. Supports mixed measurements such as 5 ft 11 in. Amount is a decimal string. Without to, returns the canonical unit for its type. Successful JSON omits reason and choices. Invalid input adds reason, and ambiguous units add choices. Use measure_units to discover accepted units. Pooled request, no separate check charge.

NameTypeReqDescription
localestring–Explicit number locale, e.g. de-DE
measurestringyesMeasurement to parse, e.g. 5 ft 11 in or 10 kg
systemstring–Resolve an ambiguous customary unit using the stated system
tostring–Target unit, e.g. cm or lb

No output schema declared.

No examples provided.

measure_units ~120

Discover the reviewed measurement units, canonical codes, types and aliases. With no filters, returns the full catalog. Pass unit to find compatible conversion targets. Combine query and type to narrow results.

NameTypeReqDescription
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
querystring–Search text, e.g. foot
typestring–Measurement type, e.g. length
unitstring–Return units compatible with this unit, e.g. m

No output schema declared.

No examples provided.

mx ~22

MX records for a domain.

NameTypeReqDescription
domainstringyesDomain name

No output schema declared.

No examples provided.

naics ~80

Compatibility name for industry. Look up a US NAICS 2022 code, title and parent hierarchy. Deep adds definition, children and exclusions on paid plans.

NameTypeReqDescription
codestringyesNAICS code, e.g. 541511 or sector range 31-33
deepboolean–Include the complete detail bag on a paid plan.

No output schema declared.

No examples provided.

naics_search ~98

Compatibility name for industry_search. Search US NAICS 2022 titles and activities. Matching text and corrections stay with the result. Deep adds definition, children and exclusions inside each result on paid plans.

NameTypeReqDescription
deepboolean–Include the complete detail bag on a paid plan.
limitinteger–Maximum results, 1-50. Default 10.
querystringyesIndustry keywords, e.g. coffee shop

No output schema declared.

No examples provided.

name ~146

Parse a name into prefix, first, middle, last and suffix. Paid deep adds gender evidence, salutation, short and directory formats, and initials. Country scopes gender evidence. name_locale selects formatting rules. Junk returns valid false.

NameTypeReqDescription
countrystring–ISO2 country context for gender, e.g. IT
deepboolean–Include the complete detail bag on a paid plan.
namestringyesThe name to parse, e.g. Smith, John or BILLY OSHALL
name_localestring–Name-formatting locale, e.g. en or ja. Defaults to en. Changes formatting only, not parsing or gender evidence.

No output schema declared.

No examples provided.

npi ~101

Validate an NPI and identify the registered provider, active/exclusion status, specialty and practice contact. Paid deep adds deactivation date and Medicare enrollment evidence.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
npistringyes10-digit NPI number

No output schema declared.

No examples provided.

phone ~103

Parse and validate a phone number with national and international display formats. Deep adds numbering-plan state and timezone on every plan. These do not locate a handset.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code for national-format numbers, e.g. US
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
numberstringyesPhone number, e.g. +14155552671

No output schema declared.

No examples provided.

point ~125

Locate coordinates in their country, state, district and actual IANA timezone. Deep adds terrain and a compact nearest-city summary on every plan. The timezone ID stays in core. Nearest city is null when none is within 200 km.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
latnumberyesLatitude in decimal degrees
lonnumberyesLongitude in decimal degrees

No output schema declared.

No examples provided.

postal ~257

Resolve a postal code to its place, coordinates and timezone. Australian core localities lists suburb choices with city, state and state_name. Null or missing means unknown, and [] means no eligible choices in the reviewed reference. A single choice can coexist with city null, so do not infer a city or a user selection. These are geographic choices, not mailing-address verification. Deep adds area, population, tax references, neighbors and metro associations on paid plans. property_tax is a nullable area statistic with annual_median, currency and period: median annual tax payable on owner-occupied homes, adjusted to the final year of the period. It is not a rate or property bill. Unsupported, missing and censored estimates are null. Tax rates are percentages and alternative geographic references, not additive.

NameTypeReqDescription
codestringyesPostal or ZIP code, e.g. SW1A 1AA, 28202
countrystring–ISO2, ISO3, or a country name. Optional when the lookup is unique.
deepboolean–Include the complete detail bag on a paid plan.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

postal_distance ~113

Distance between two postal codes. Deep adds metropolitan associations inside each endpoint on paid plans.

NameTypeReqDescription
countrystring–ISO2, ISO3, or a country name. Optional when the lookup is unique.
deepboolean–Include the complete detail bag on a paid plan.
fromstringyesFirst postal code
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
tostringyesSecond postal code

No output schema declared.

No examples provided.

postal_nearby ~132

Find nearby postal codes with distances. Deep adds metropolitan associations to the origin and each result on paid plans.

NameTypeReqDescription
codestringyesPostal code to search around
countrystring–ISO2, ISO3, or a country name. Optional when the lookup is unique.
deepboolean–Include the complete detail bag on a paid plan.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
radiusnumber–Search radius
unitstring–Radius unit, default km

No output schema declared.

No examples provided.

preflight ~159

Estimate whether your secret key permits a proposed Email, VAT, Carrier, Caller, HLR, Domain, DNS, MX, Country, IP, Phone or Postal task, its advisory capacity, and additional USD charges under accepted terms. Supply operation counts and optional Deep, without lookup inputs. Uses default SDK retries: up to three attempts per ordinary lookup and one per metered lookup. Authenticated metadata request, no lookup units or paid checks. Reserves no units or money and does not enforce a budget. Check permitted, cost.status, capacity and budget before lookup.

NameTypeReqDescription
budget_usdstring–Optional USD budget as a decimal string, e.g. 2.50. Advisory, never an enforced cap.
operationsarrayyes–

No output schema declared.

No examples provided.

provider ~278

Look up an NPI in stored provider-directory sources. valid is format/checksum only; registered means found in the NPPES snapshot; active is recorded NPI activation, not licensure. excluded is an NPI-only OIG LEIE match, and false is not complete exclusion clearance. Returns identity, specialty and practice contact where held. Paid deep adds all published taxonomies and reported license details, provider enumeration/update/reactivation dates, deactivation date, Medicare enrollment, opt-out and enrollment rows. Reported licenses are not verified licenses; provider update dates are not source freshness. Null means unknown. No live credential or payment-eligibility verification. Pooled request; no separate check meter.

NameTypeReqDescription
deepboolean–Include taxonomies, enumerated_at, updated_at, reactivated_at, deactivated_at, medicare, opt_out and enrollments from stored sources on paid plans. Omitted by default; Free returns {}. Null lists are…
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
npistringyesOriginal NPI input as a string, normally 10 digits. Preserve the input; invalid values return valid=false with unknown provider fields. Do not URI-decode it.

No output schema declared.

No examples provided.

stack ~191

Identify website technologies and available versions by category. Requires a hostname only. CMS, servers, frameworks, ecommerce, analytics, chat, payments and hosting are arrays of technology, name and nullable version. checked_at gives the check time. Scope is homepage or site; pages counts successfully checked HTML pages. Partial is true for homepage-only or incomplete bounded checks, false only when known in-scope candidates finished, never a guarantee every page was visited. When no page could be checked, checked_at and all categories are null, pages is 0 and partial is null. Empty arrays mean no matches. Missing detections do not prove absence. Uses one request from the plan allowance. Successful checks may be reused for up to 24 hours.

NameTypeReqDescription
domainstringyesPublic website hostname only, e.g. example.com. No scheme, path, port or IP address.
prettyboolean–Format the JSON response.

No output schema declared.

No examples provided.

state ~124

Look up a state or province by code or name. Deep adds its demographic and tax profile on paid plans. Pass country to resolve a colliding code.

NameTypeReqDescription
codestringyesState code or name, e.g. colorado, NC
countrystring–ISO2, ISO3, or a country name. Optional when the lookup is unique.
deepboolean–Include the complete detail bag on a paid plan.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

state_districts ~119

List the districts, counties or departments of a state. Deep adds population to each result on paid plans.

NameTypeReqDescription
codestringyesState code or name, e.g. NC, colorado
countrystring–ISO2, ISO3, or a country name. Optional when the lookup is unique.
deepboolean–Include population in each district detail bag on a paid plan.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.

No output schema declared.

No examples provided.

tariff ~270

Look up a US tariff code, description, lineage, published base general rate, exact edition and answering date. Paid deep adds schedule columns, units and matched Chapter 99 measures. Origin is the country where goods originate, not the shipping country. Optional edition pins immutable source bytes. Optional date requires verified source coverage; edition without date returns date null and no effective rate. Default requests use today. deep.reason explains a null effective_rate, including incomplete_coverage; null never means zero. Matched measures are inspectable candidates, not complete duty or landed cost.

NameTypeReqDescription
codestringyesUS HTS code: 4, 6, 8 or 10 ASCII digits, dots and whitespace optional, e.g. 8471.30.01.00
datestring–YYYY-MM-DD with verified source coverage. Combine with edition only when it covers this date.
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
editionstring–Exact edition returned by Tariff, such as ted_3. Without date, returns undated schedule context.
originstring–ISO 3166-1 alpha-2 country where the goods originate, not the shipping country; only read with deep, e.g. US

No output schema declared.

No examples provided.

tariff_search ~151

Search US tariff schedule descriptions by product words. Returns up to 20 candidate lines with hts, description, general rate and parent lineage, plus the exact edition and answering date. Optional edition pins immutable source bytes. Optional date requires verified source coverage; combine only when that edition covers the date. Edition without date returns date null. Description search is not product classification.

NameTypeReqDescription
datestring–YYYY-MM-DD with verified source coverage. Combine with edition only when it covers this date.
editionstring–Exact edition returned by Tariff, such as ted_3. Without date, returns undated schedule context.
querystringyesProduct words, e.g. sunglasses, laptop, coffee

No output schema declared.

No examples provided.

task_cancel ~42

Prevent new lookups in this task. Already started lookups may finish and incur their reserved charge. Saved results remain recoverable.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

task_create ~137

Create a 24-hour task with allowed operations, lookup counts and an enforced USD limit on additional lookup charges. Requires already authorized user scope and a secret key. Reserves no account units and makes no lookups. Only task_lookup obeys this task budget. Ordinary lookups remain separate. Included units can make actual cost zero, but a positive-rate lookup needs budget room for its conservative full rate.

NameTypeReqDescription
budget_usdstringyes–
operationsarrayyes–
request_idstringyesUnique ID for the intended request. Reuse this exact ID and inputs on every retry. Never include private lookup values in it.

No output schema declared.

No examples provided.

task_lookup ~168

Run one lookup under an authorized task budget and count. Reuse request_id with identical inputs to recover its saved response without another lookup or usage charge. Inspect status_code and result, including nulls. task_in_progress or task_outcome_unknown means keep the same request_id; never use a new ID to repeat uncertain work. Saved results are available for 48 hours from task creation. This tool can consume pooled and metered units on its first execution.

NameTypeReqDescription
countrystring––
deepboolean––
operationstringyes–
request_idstringyesUnique ID for the intended request. Reuse this exact ID and inputs on every retry. Never include private lookup values in it.
task_idstringyes–
valuestringyes–

No output schema declared.

No examples provided.

task_status ~37

Read completed and allocated lookup counts, spent and reserved USD budget and expiry. No lookup or usage unit.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

time ~572

Current local time, Unix seconds, exact offset and DST. Use an IANA zone, both coordinates, or one explicit IP, city, country, airport, port or address selector. Omit all for UTC. Ambiguous or missing locations return null clock fields with location candidates; never choose a candidate for the user. to or targets converts one instant. Deep adds wall-time resolution, standard/seasonal offsets and actual DST-season transitions on every plan.

NameTypeReqDescription
addressstring–Full address with explicit country. Strict point matches are currently supported for US; ambiguity stays unresolved.
atstring–ISO 8601 time, default now. With to or targets, a time without a UTC offset is source wall time. Otherwise it is UTC. Include an offset to disambiguate a repeated local time
citystring–Exact city name or stable city_ identifier. Country and state can narrow candidates.
countrystring–ISO2 country as the source, or context with city/address. Multiple country timezones remain candidates.
deepboolean–Include optional detail on every plan.
disambiguationstring–For offsetless at with to or targets at a clock change. Default compatible chooses the earlier repeated time or advances a skipped time. earlier and later choose the respective instant. For user-ente…
iatastring–Three-letter IATA airport identifier.
icaostring–Four-letter ICAO airport identifier.
ipstring–Explicit IPv4 or IPv6 input. Never use a hosted server IP as the user location.
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
latnumber–Latitude in decimal degrees
lonnumber–Longitude in decimal degrees
statestring–State context with city/address and country, as a bare code or matching country-prefixed code.
targetsarray–Destination IANA IDs, preserving order and duplicates. Use instead of to. All targets share one instant. An unresolved or ambiguous source returns targets null.
timezonestring–IANA timezone, e.g. America/New_York. Omit for UTC when all source selectors are absent
tostring–Destination IANA timezone, e.g. Asia/Tokyo. Returns to.at and to.unix at the same instant
unlocodestring–UN/LOCODE port identifier. Results use the reviewed port reference, not every assigned UN/LOCODE.

No output schema declared.

No examples provided.

time_zones ~299

Search serving IANA timezone identifiers. Filter by country, IANA area, exact offset, abbreviation or DST facts at one instant. Abbreviations return candidate identifiers and never choose a timezone. Empty timezones means no match. Details adds aligned rows and the evaluation instant. One pooled request.

NameTypeReqDescription
abbreviationstring–Timezone abbreviation to find candidates for, e.g. CST. Never infer a unique zone from an abbreviation.
areastring–IANA identifier prefix, e.g. America.
atstring–ISO instant for all filters and detailed rows. Default now. Offsetless input means UTC.
countrystring–ISO2 country association, e.g. US.
detailsboolean–Include zones rows with country associations, area, offset, abbreviation and DST facts, plus the common evaluation instant.
dstboolean–Whether the rule DST flag is active at the selected instant. Includes negative seasonal adjustments.
observes_dstboolean–Whether a DST-flagged state occurs during the UTC calendar year containing at.
offsetstring–Exact UTC offset at the selected instant, e.g. +05:45 or +00:09:21.
querystring–Identifier search, e.g. New York or Europe. Spaces and underscores match the same way.
sortstring–Order by identifier (default) or actual UTC offset, then identifier.

No output schema declared.

No examples provided.

timezone ~220

Compatibility tool; use time for new integrations. Look up a timezone from an IANA id or from lat and lon. Offset, DST, local time. Pass at for a specific instant. Pass to with another IANA id to convert a time between zones: the response appends at (wall time in the from zone) and to.at (the converted time). Open ocean answers the nautical Etc/GMT zone.

NameTypeReqDescription
atstring–ISO 8601 time, default now. With to and no UTC offset, reads as wall time in the from zone
langstring–Optional display language, such as fr or zh-Hant. IDs, numeric values and input parsing stay unchanged.
latnumber–Latitude in decimal degrees
lonnumber–Longitude in decimal degrees
timezonestring–IANA timezone id, e.g. America/New_York
tostring–Convert: the other IANA zone, e.g. Asia/Tokyo. Requires timezone, not lat/lon

No output schema declared.

No examples provided.

useragent ~56

Parse a User-Agent string: browser, OS, device, bot detection.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
uastringyesThe User-Agent string to parse

No output schema declared.

No examples provided.

vat ~130

Validate a VAT number: format and checksum on every call. Deep asks the live EU registry for registered, legal name, and address. Pass from with your own VAT for a consultation identifier.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code when the number has no prefix, e.g. US
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
fromstring–Your own VAT number. Returns a consultation identifier for your audit file
numberstringyesVAT number, with or without the country prefix

No output schema declared.

No examples provided.

vehicle ~89

Identify a vehicle by VIN: year, make, model, trim, body and vehicle type. Paid deep adds specifications, manufacturing detail and model-level recall campaigns. These do not establish whether this VIN needs a repair.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
vinstringyesThe VIN as you have it. Spaces and punctuation fold out

No output schema declared.

No examples provided.

vin ~81

Compatibility entry for vehicle. Decode a VIN to year, make, model, trim, body and vehicle type. Paid deep adds specifications, manufacturing detail and model-level recall campaigns.

NameTypeReqDescription
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
vinstringyesThe VIN as you have it. Spaces and punctuation fold out

No output schema declared.

No examples provided.

weather ~131

Current weather with observation time and station distance. Paid deep adds specialist current measurements, forecast, alerts, hourly and daily outlook, air quality and optional history. Metric and imperial pairs stay together. A date requires paid deep and adds the past UTC day in deep.history alongside current conditions.

NameTypeReqDescription
datestring–A past UTC day, YYYY-MM-DD. Requires paid deep. Adds deep.history alongside current conditions.
deepboolean–Include the nested deep object when available. Pricing depends on the operation.
latnumberyesLatitude in decimal degrees
lonnumberyesLongitude in decimal degrees

No output schema declared.

No examples provided.

Install

How do I install the ParseAPI MCP server?

ParseAPI runs locally as an npm package, launched with npx -y parseapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · parseapi-mcp

# add to Claude Code
claude mcp add com-parseapi-mcp -- npx -y parseapi-mcp
Common questions

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 npm package (parseapi-mcp).

Is the ParseAPI MCP server safe to use?

ParseAPI scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 89 tools: measure, measure_units, ip, ip_self, continent, and 84 more. Their descriptions and schemas cost roughly 14,066 tokens of context every time the server is loaded.

Is the ParseAPI MCP server still maintained?

ParseAPI is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ParseAPI MCP server under?

ParseAPI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.