--- title: "Tallyfy MCP server | Agent MCP Directory" description: "Tallyfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity." canonical: https://agentmcpdirectory.com/directory/tallyfy-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Tallyfy MCP server | Agent MCP Directory > Tallyfy: sign-in required (OAuth DCR), tools not seen, not counted as an MCP server. Directory entry with sources. Category: Productivity. Source: https://agentmcpdirectory.com/directory/tallyfy-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Tallyfy: MCP server, CLI and agent surfaces Sign-in required, tools not seen, not counted. The MCP endpoint listed for Tallyfy at mcp.tallyfy.com answered 401 with OAuth metadata on 4 November 2026. Its tools can be listed only after a person authorizes a client, and this directory never signs in. ## Fact sheet | Company | Tallyfy (registry title: Tallyfy Workflow Automation) | | --- | --- | | Domain | tallyfy.com | | Category | Productivity (assigned by this directory from the registry description) | | MCP server | Sign-in required (OAuth with client registration) | | Ora score | none: Ora returned no cached score for tallyfy.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.tallyfy.com/ | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 401 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 1,318 ms over 1 attempt | The endpoint answered the handshake with a sign-in challenge, so the tool list is not visible to this directory. It is not counted as an MCP server: a sign-in challenge is its own state, and the connector listed no tools. ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:59:48Z https://mcp.tallyfy.com/ sent initialize result auth-required (HTTP 401) 1295 ms - 20:04:46Z https://mcp.tallyfy.com/ sent initialize result auth-required (HTTP 401) 1318 ms ## Authentication | Auth type | OAuth with client registration | | --- | --- | | What the challenge said | Bearer realm="https://mcp.tallyfy.com", resource_metadata="https://mcp.tallyfy.com/.well-known/oauth-protected-resource", error="invalid_token", error_description="No bearer token was presented. This endpoint requires an OAuth 2.1 access token. Discover the authorization server at https://mcp.tallyfy.com/.well-known/oauth-protected-resource, complete the OAuth flow, then retry the request with an Authorization: Bearer header." | | Protected resource metadata | mcp.tallyfy.com | | Authorization server metadata | mcp.tallyfy.com | | Registration endpoint | https://mcp.tallyfy.com/mcp/oauth/register | ### The sign-in route, step by step 1. Request `https://mcp.tallyfy.com/` without a token. It answers 401 and a `WWW-Authenticate` header. 2. Read the protected resource metadata at `https://mcp.tallyfy.com/.well-known/oauth-protected-resource` to find the authorization server. 3. Register a client at the registration endpoint `https://mcp.tallyfy.com/mcp/oauth/register` (dynamic client registration), so no human has to create an app first. 4. Send a person through the authorization page, then retry the endpoint with the bearer token. The connector stops after step 2 and never authorizes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Tallyfy. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.tallyfy/mcp-server | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/tallyfy-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=tallyfy), read 4 November 2026 - [Tallyfy website](https://tallyfy.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026