MCP.Market

Tax Regulations MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/tax-regulations·v0.2.0

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Tax Regulations yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Tax Regulations tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Tax Regulations compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
250 ms
faster than 55% of 30,031 servers

Release history: 3 versions in the registry since 2026-07-26, latest 2026-10-29, typically one every 61 days.

Install Tax Regulations in Claude Code, Cursor or VS Code

claude mcp add --transport http tax-regulations https://gateway.pipeworx.io/tax-regulations/mcp
Add to Cursor

What the publisher says

From the Tax Regulations repository's README, as published. We do not edit it. Read it on GitHub

mcp-tax-regulations

Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, "Treas. Reg.").

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "tax-regulations": {
      "url": "https://gateway.pipeworx.io/tax-regulations/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/tax-regulations/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Tax Regulations: common questions

Is Tax Regulations MCP server safe?
Mostly: it is graded B (77/100). Read the Tax Regulations safety report
How do I install Tax Regulations?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Tax Regulations need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Tax Regulations maintained?
The last commit was 47 days ago (2026-09-18). The latest release is v0.2.0.
Is Tax Regulations up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Tax Regulations compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 250 ms (faster than 55% of 30,031 servers). Full comparison.

More from pipeworx-io →