Pin Seeker
REMOTE · PINSEEKER.XYZ · SCANNED SEP 20
Search golf tee times by natural language. Returns GolfNow booking links. Does not book or hold.
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 251 tokens (~251/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 Pin Seeker MCP server?
Pin Seeker is a hosted endpoint at https://pinseeker.xyz/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 · pinseeker.xyz
claude mcp add --transport http xyz-pinseeker-tee-times 'https://pinseeker.xyz/mcp'
{
"mcpServers": {
"xyz-pinseeker-tee-times": {
"url": "https://pinseeker.xyz/mcp"
}
}
} {
"servers": {
"xyz-pinseeker-tee-times": {
"type": "http",
"url": "https://pinseeker.xyz/mcp"
}
}
} [mcp_servers.xyz-pinseeker-tee-times] url = "https://pinseeker.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-pinseeker-tee-times": {
"type": "remote",
"url": "https://pinseeker.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-pinseeker-tee-times --url 'https://pinseeker.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-pinseeker-tee-times:
url: "https://pinseeker.xyz/mcp" {
"McpServers": {
"xyz-pinseeker-tee-times": {
"Transport": "http",
"Url": "https://pinseeker.xyz/mcp"
}
}
} assistant mcp add xyz-pinseeker-tee-times -t streamable-http -u 'https://pinseeker.xyz/mcp'
{
"mcpServers": {
"xyz-pinseeker-tee-times": {
"type": "http",
"url": "https://pinseeker.xyz/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.
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 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.
- 12 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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://pinseeker.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pinseeker.xyz | CN=WR3,O=Google Trust Services,C=US | 7 Aug 2026 | 5 Nov 2026 | RSA 2048 | SHA256-RSA | 3dec5d5c9a90090ae81cfe5eaa22b8 |
| SANs: pinseeker.xyz | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pinseeker.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| pinseeker.xyz. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pinseeker.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://pinseeker.xyz/mcp | HTTPS enforced | 301 | https://pinseeker.xyz/mcp |
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 →
search_tee_times Search golf tee times ~152
Search golf tee times, hot deals, and cheapest rounds by city, ZIP, or course name. Use for tee times, booking a round, weekend golf, twilight, or comparing courses nearby. No GolfNow FacilityId needed. Returns booking URLs (course Book handoff or GolfNow). Opening Book starts course checkout and may hold a slot; Pin Seeker does not pay. Ask for a city/ZIP/course and date if missing.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Natural language search, e.g. "Saturday morning near San Francisco for 2" or "Harding Park tomorrow afternoon" |
| userTimezone | string | – | IANA timezone of the golfer, e.g. America/Los_Angeles |
No output schema declared.
No examples provided.
What is the Pin Seeker MCP server?
Pin Seeker is an MCP server listed in the public MCP registry as xyz.pinseeker/tee-times. Search golf tee times by natural language. Returns GolfNow booking links. Does not book or hold. This page covers its hosted endpoint (https://pinseeker.xyz/mcp).
Is the Pin Seeker MCP server safe to use?
Pin Seeker scores 88 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 Pin Seeker MCP server expose?
Pin Seeker exposes 1 tool: search_tee_times. Their descriptions and schemas cost roughly 152 tokens of context every time the server is loaded.
Does the Pin Seeker MCP server require authentication?
No. We connected to Pin Seeker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pin Seeker MCP server still maintained?
Pin Seeker 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.