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.

io.github.ptrinh/freeport-nostr

NPM · FREEPORT-NOSTR-MCP · 2 COMPONENTS · SCANNED SEP 21

Search Freeport Nostr events by kind, tag & geohash radius (rides, services, reputation).

0 this week 82 Trust /100
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 Security98
  • 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
  • 45 of 126 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 952 tokens (~136/item across 7 items; 5 tools + 2 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 Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% 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 5 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
Install

How do I install the io.github.ptrinh/freeport-nostr MCP server?

io.github.ptrinh/freeport-nostr runs locally as an npm package, launched with npx -y freeport-nostr-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 · freeport-nostr-mcp

# add to Claude Code
claude mcp add ptrinh-freeport-nostr -- npx -y freeport-nostr-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ptrinh-freeport-nostr": {
      "command": "npx",
      "args": [
        "-y",
        "freeport-nostr-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ptrinh-freeport-nostr": {
      "command": "npx",
      "args": [
        "-y",
        "freeport-nostr-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ptrinh-freeport-nostr -- npx -y freeport-nostr-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ptrinh-freeport-nostr": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "freeport-nostr-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ptrinh-freeport-nostr --command npx --arg -y --arg freeport-nostr-mcp
# ~/.hermes/config.yaml
mcp_servers:
  ptrinh-freeport-nostr:
    command: "npx"
    args: ["-y", "freeport-nostr-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ptrinh-freeport-nostr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "freeport-nostr-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ptrinh-freeport-nostr -t stdio -c npx -a -y freeport-nostr-mcp
// mcp.json
{
  "mcpServers": {
    "ptrinh-freeport-nostr": {
      "command": "npx",
      "args": [
        "-y",
        "freeport-nostr-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 18 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 17 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 Sept 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.

  • 12 Sept 26 +1

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

  • 10 Sept 26 −2
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → 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 21 Sept 2026 · Analysed npm/freeport-nostr-mcp@0.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 126 packages
Packages resolved 126
Stale 45
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~745 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
nostr_get_event ~62

Fetch one or more events by id. Returns the raw signed events.

NameTypeReqDescription
idsarrayyes
relaysarrayOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.

No output schema declared.

No examples provided.

nostr_profile ~145

Fetch NIP-01 profile metadata (kind 0) for one or more pubkeys — name, about, picture, nip05, lud16, etc. Optionally include each author's most recent notes (kind 1). General-purpose: works for any Nostr user, not just Freeport.

NameTypeReqDescription
pubkeysarrayyesHex pubkeys to fetch profiles for.
recentNotesintegerIf >0, also fetch up to this many recent text notes (kind 1) per pubkey.
relaysarrayOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.

No output schema declared.

No examples provided.

nostr_query_raw ~157

Escape hatch: run an arbitrary NIP-01 filter (kinds/authors/ids/tags/since/until/limit). Use the typed tools above when they fit. Returns raw signed events.

NameTypeReqDescription
authorsarray
idsarray
kindsarray
limitinteger
relaysarrayOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.
sinceinteger
tagsobjectTag filters, e.g. {"t":["vn_hanoi"],"g":["w3gv"]}. Keys are single tag letters.
untilinteger

No output schema declared.

No examples provided.

nostr_search_intents ~251

Search Freeport ride/service/product intents (offers & requests). Filter by side, category/area topic tags, and an optional geographic radius. Results are decoded, expiry-filtered, and sorted nearest-first when a point is given.

NameTypeReqDescription
includeExpiredboolean
limitinteger
nearobjectFilter & sort by distance from this point.
relaySideGeohashbooleanAlso narrow at the relay via a #g cover of the radius. Only effective if posts carry geohash-prefix tags; off by default.
relaysarrayOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.
sidestringoffer = drivers/providers/sellers; request = riders/buyers; any = both
sinceintegerOnly events created at/after this unix-seconds time.
topicsarrayTopic `t` tags to require (category/subcategory/area keys, e.g. "vn_hanoi", "ridesharing").
untilintegerOnly events created at/before this unix-seconds time.

No output schema declared.

No examples provided.

nostr_search_reputation ~130

Fetch reputation signals for a pubkey: karma ratings (kind 32103) it received and deal receipts (kind 32104). Returns proven-deal count (both receipt halves present) and a karma summary. Note: scores are subjective and un-weighted here; do not treat as Sybil-proof.

NameTypeReqDescription
limitinteger
pubkeystringyesSubject pubkey (hex) to look up reputation for.
relaysarrayOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.

No output schema declared.

No examples provided.

Common questions

What is the io.github.ptrinh/freeport-nostr MCP server?

io.github.ptrinh/freeport-nostr is an MCP server listed in the public MCP registry as io.github.ptrinh/freeport-nostr. Search Freeport Nostr events by kind, tag & geohash radius (rides, services, reputation). This page covers its npm package (freeport-nostr-mcp).

Is the io.github.ptrinh/freeport-nostr MCP server safe to use?

io.github.ptrinh/freeport-nostr scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.ptrinh/freeport-nostr MCP server expose?

io.github.ptrinh/freeport-nostr exposes 5 tools: nostr_search_intents, nostr_search_reputation, nostr_get_event, nostr_profile, nostr_query_raw. Their descriptions and schemas cost roughly 745 tokens of context every time the server is loaded.

Is the io.github.ptrinh/freeport-nostr MCP server still maintained?

io.github.ptrinh/freeport-nostr is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.ptrinh/freeport-nostr MCP server under?

io.github.ptrinh/freeport-nostr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.