Skip to content
Pin Seeker logo

Pin Seeker

Turns a plain-English request into golf tee time search results that a group can book or share.

Actively maintained

At a glanceswept Oct 26, 2026

≈ 4visits/mo

Little sign of use · estimate, read Oct 15, 2026

For
Golfers and foursomes looking for a nearby tee time that fits their day, time, and budget.
Activity
Actively maintainedrelease 3 weeks ago
App Store
59 ratingsiPhone & iPad · updated Oct 7, 2026
Used for
  • find a tee time from a plain-English request
  • filter tee times by day, time, and price
  • book or share a round with a group
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 20, 2026
  • MCP serverxyz.pinseeker/tee-timesverified in the MCP registry
  • Stateanswers, 1 toolschecked 2026-10-20
  • Address to connectpinseeker.xyz/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Pin Seeker for?

Sign in to leave a note
Questions this page answers
  • What is Pin Seeker?

    Turns a plain-English request into golf tee time search results that a group can book or share.

  • Who is Pin Seeker for?

    Golfers and foursomes looking for a nearby tee time that fits their day, time, and budget.

  • Do people use Pin Seeker?

    Little sign of use: ≈ 4 visits/mo · estimate, 2026-10.

  • Is Pin Seeker still maintained?

    Actively maintained: release 3 weeks ago.

  • Does Pin Seeker have an iPhone app?

    Yes: “Pin Seeker” on the App Store, rated 5 from 9 ratings; current version released 2026-10-07.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk