io.github.ptrinh/freeport-nostr
REMOTE · NOSTR-MCP.TRINH.UK · 2 COMPONENTS · SCANNED SEP 22
Search Freeport Nostr events by kind, tag & geohash radius (rides, services, reputation).
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 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 1388 tokens (~173/item across 8 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
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; "freeport_create_post" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 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 io.github.ptrinh/freeport-nostr MCP server?
io.github.ptrinh/freeport-nostr is a hosted endpoint at https://nostr-mcp.trinh.uk/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 · nostr-mcp.trinh.uk
claude mcp add --transport http ptrinh-freeport-nostr 'https://nostr-mcp.trinh.uk/mcp'
{
"mcpServers": {
"ptrinh-freeport-nostr": {
"url": "https://nostr-mcp.trinh.uk/mcp"
}
}
} {
"servers": {
"ptrinh-freeport-nostr": {
"type": "http",
"url": "https://nostr-mcp.trinh.uk/mcp"
}
}
} [mcp_servers.ptrinh-freeport-nostr] url = "https://nostr-mcp.trinh.uk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ptrinh-freeport-nostr": {
"type": "remote",
"url": "https://nostr-mcp.trinh.uk/mcp",
"enabled": true
}
}
} openclaw mcp add ptrinh-freeport-nostr --url 'https://nostr-mcp.trinh.uk/mcp' --transport streamable-http
mcp_servers:
ptrinh-freeport-nostr:
url: "https://nostr-mcp.trinh.uk/mcp" {
"McpServers": {
"ptrinh-freeport-nostr": {
"Transport": "http",
"Url": "https://nostr-mcp.trinh.uk/mcp"
}
}
} assistant mcp add ptrinh-freeport-nostr -t streamable-http -u 'https://nostr-mcp.trinh.uk/mcp'
{
"mcpServers": {
"ptrinh-freeport-nostr": {
"type": "http",
"url": "https://nostr-mcp.trinh.uk/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.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
- 26 Jul 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 21 Sept 2026 · Probed https://nostr-mcp.trinh.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trinh.uk | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 50d6bf265b951cc9131441e26b17aacc |
| SANs: trinh.uk, *.trinh.uk | ||||||
| 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 secure
Validation of nostr-mcp.trinh.uk. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| trinh.uk. | present | 2371 | 13 | Verified |
| nostr-mcp.trinh.uk. | Verified address RRset verified with the apex keys |
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://nostr-mcp.trinh.uk/mcp | Verified | 200 | |
| http (plaintext) | http://nostr-mcp.trinh.uk/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 →
freeport_create_post ~415
Publish a Freeport intent — an OFFER (side "offer": driver/provider/seller) or a REQUEST (side "request": rider/buyer). Provide EITHER a `secretKey` (nsec or hex — the server builds, signs and publishes; use a DEDICATED agent key, never a personal one — it is used once and never stored) OR a pre-signed `event` (you sign locally; nothing secret reaches the server). Strict rate limits apply. Returns the published event id + addressable `d`.
| Name | Type | Req | Description |
|---|---|---|---|
| d | string | – | Stable id to republish/replace an existing post; defaults to random. |
| event | – | – | A complete, signed Nostr event (kind 32101/32102). Use instead of secretKey to keep keys off the server. |
| expiresInMinutes | integer | – | How long the post stays live (default 720). Max 30 days. |
| geohashes | array | – | Geohashes for location-scoped discovery. Each is expanded into all its prefixes (precision 1-6) so radius searches at any precision match. |
| market | string | – | Market key, e.g. "rideshare" or "service". |
| payload | object | – | Intent payload (from/to/location, payment, etc.) per the freeport://protocol resource. |
| relays | array | – | – |
| schema | string | – | Payload schema, e.g. "rideshare/1" or "service/1". |
| secretKey | string | – | nsec or 64-hex private key. Used transiently to sign; never stored. Omit if passing a pre-signed `event`. |
| side | string | – | offer = provider/seller/driver; request = buyer/rider. |
| title | string | – | – |
| topics | array | – | Topic `t` tags (area/category), e.g. ["vn_hanoi","vn_hanoi_ridesharing"]. |
| window | object | – | – |
No output schema declared.
No examples provided.
nostr_get_event ~62
Fetch one or more events by id. Returns the raw signed events.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
| relays | array | – | Override 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.
| Name | Type | Req | Description |
|---|---|---|---|
| pubkeys | array | yes | Hex pubkeys to fetch profiles for. |
| recentNotes | integer | – | If >0, also fetch up to this many recent text notes (kind 1) per pubkey. |
| relays | array | – | Override 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.
| Name | Type | Req | Description |
|---|---|---|---|
| authors | array | – | – |
| ids | array | – | – |
| kinds | array | – | – |
| limit | integer | – | – |
| relays | array | – | Override the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays. |
| since | integer | – | – |
| tags | object | – | Tag filters, e.g. {"t":["vn_hanoi"],"g":["w3gv"]}. Keys are single tag letters. |
| until | integer | – | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| includeExpired | boolean | – | – |
| limit | integer | – | – |
| near | object | – | Filter & sort by distance from this point. |
| relaySideGeohash | boolean | – | Also narrow at the relay via a #g cover of the radius. Only effective if posts carry geohash-prefix tags; off by default. |
| relays | array | – | Override the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays. |
| side | string | – | offer = drivers/providers/sellers; request = riders/buyers; any = both |
| since | integer | – | Only events created at/after this unix-seconds time. |
| topics | array | – | Topic `t` tags to require (category/subcategory/area keys, e.g. "vn_hanoi", "ridesharing"). |
| until | integer | – | Only 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| pubkey | string | yes | Subject pubkey (hex) to look up reputation for. |
| relays | array | – | Override the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays. |
No output schema declared.
No examples provided.
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 hosted endpoint (https://nostr-mcp.trinh.uk/mcp).
Is the io.github.ptrinh/freeport-nostr MCP server safe to use?
io.github.ptrinh/freeport-nostr scores 73 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 io.github.ptrinh/freeport-nostr MCP server expose?
io.github.ptrinh/freeport-nostr exposes 6 tools: nostr_search_intents, nostr_search_reputation, nostr_get_event, nostr_profile, nostr_query_raw, freeport_create_post. Their descriptions and schemas cost roughly 1,160 tokens of context every time the server is loaded.
Does the io.github.ptrinh/freeport-nostr MCP server require authentication?
No. We connected to io.github.ptrinh/freeport-nostr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.