Skip to content

Tallyho MCP server

so.tallyho/tallyhotallyho.sostreamable-httpv1.0.0Scanned

Licensed plumbers near a job in SF, Oakland, Berkeley and the Tri-Valley, with a booking handoff.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 1 finding, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Tallyho MCP server can do

The Tallyho MCP server is published by tallyho.so, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: book and report), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (book).

The fixed checks matched 1 finding, 1 of them high severity (model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • bookBook a plumber from a find (business_id + find_id).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a destination (input.channel): what the tool writes goes there.
    Description, as the server wrote it
    Book a plumber from a find (business_id + find_id). Version 1 is a handoff: Tallyho records the request and returns the plumber's phone number and the questions to ask; nothing is booked until the user calls, so booked is false. Don't send the user's contact details on a handoff; they are never stored either way. Keep the booking_id and call report after the call to the plumber, and again after the job.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • reportReport on a booking, by booking_id, from any session.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Report on a booking, by booking_id, from any session. After the call to the plumber: result confirmed, declined or not_booked, plus the quote (price, slot). After the job: completed, not_completed, no_show or a cancellation, plus the final price and arrival time. Verdicts per promise are kept, broken or unobserved; Tallyho computes price and timing verdicts from the figures. Kept and broken are final. Returns the plumber's updated likelihoods and, if the booking fell through, the next best plumbers from the same search.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • findFind plumbers for a job in San Francisco, Oakland, Berkeley and the Tri-Valley (Danville, San Ramon, Dublin, Pleasanton, Livermore), ranked by the chance they keep every promise th…No findings

    Why it is in this group

    • The name "find" says "find": a word for reading.
    Description, as the server wrote it
    Find plumbers for a job in San Francisco, Oakland, Berkeley and the Tri-Valley (Danville, San Ramon, Dublin, Pleasanton, Livermore), ranked by the chance they keep every promise that matters for it: take the job, have a slot in the window, quote within budget, arrive on time, hold the quote, finish, no upsell. Only job.location.zip is required; add system, issue, urgency, window and price_ceiling_cents for a sharper answer. Each candidate has a likelihood per promise with n (the evidence behind it), an 80% interval and freshness, the joint likelihood, and its CSLB license check. n=0 is Tallyho's starting estimate, not a measurement. Free; never contacts a business. Next: book a candidate with this find_id.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • statusRead a booking as it stands, by booking_id, from any session; holding the booking_id is enough.1 finding

    Why it is in this group

    • The name "status" says "status": a word for reading.

    Findings

    • High

      The description contains "Never tell the user", an instruction to keep something from the user.

      Matched text

      description: "...and stop when check_after_s is absent. Never tell the user a job is booked unless booked is true...."

      What this check looks for
    Description, as the server wrote it
    Read a booking as it stands, by booking_id, from any session; holding the booking_id is enough. Works on every booking, handoff ones too. On a booking Tallyho is calling about, status moves from requested to confirmed, counter, declined, not_booked or pending: call status again after check_after_s seconds, and stop when check_after_s is absent. Never tell the user a job is booked unless booked is true. Returns the quote once known, the reason a booking fell through or was countered, the promises still to report, and, if it fell through, the next best plumbers from the same search. Reads only; never contacts a business.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:20 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tallyho.so/mcp/v1: tools/list returned 4 tools to an anonymous client, including book (write), report (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high
  • Highstatus

    The description contains "Never tell the user", an instruction to keep something from the user.

    Matched text

    description: "...and stop when check_after_s is absent. Never tell the user a job is booked unless booked is true...."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tallyho https://mcp.tallyho.so/mcp/v1
claude mcp add --transport http tallyho https://mcp.tallyho.so/mcp/v1

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tallyho__find",
      "mcp__tallyho__status"
    ],
    "ask": [
      "mcp__tallyho__book",
      "mcp__tallyho__report"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tallyho. Review it before you use it.

Capability tags behind 1 rule
  • mcp__tallyho__book outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/so.tallyho/tallyho/verify?hash=2b9c00c0e22f813591818ab7ab1eeb2be25dbbf3a668119125afd2e57b1f14f5" | jq -e '.changed == false'

Pinned hash 2b9c00c0e22f, from Nov 21, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/so.tallyho/tallyho/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for so.tallyho/tallyho
[![Anlyon Radar](https://radar.anlyon.com/badge/so.tallyho/tallyho.svg)](https://radar.anlyon.com/servers/so.tallyho/tallyho)

Source: MCP Registry. Synced Nov 21, 2026, 04:17 UTC.

Tallyho MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tallyho MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 1 finding (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tallyho MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Tallyho MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tallyho MCP server have?

4 tools: 2 write, 2 read. book, report, find and status.

Does the Tallyho MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Tallyho MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): book.

Has the Tallyho MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.