Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Mit Google anmelden, um Bewertungen zu schreiben.Prototyp · alle 30 Min. aktualisiert
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

Tennessee Code

von pipeworx-ioVersion 0.2.1i★ 1iComputer oder Cloud
Name in der Registryio.github.pipeworx-io/tennessee-code

So installierst du es

What it does

Tennessee Code Annotated (T.C.A.) — Tennessee state statutes by citation and by topic. Fleet #2885.

  • Connects Computer oder Cloud
  • Account or key No key needed
  • Category Entwicklertools

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

5/5 Prüfungen bestanden · Was du fragst, läuft über den Server des Anbieters (gateway.pipeworx.io) · ✓ Befehle geprüft am 14. Nov. 2026

Zuerst: Welche KI nutzt du?

Wähle deine App, dann erscheinen die Schritte unten.

Klappt mit Claude · etwa 2 Min.

Kein Schlüssel, nichts zu installieren · Einmal auf claude.ai oder in der Desktop-App einrichten, dann im Chat nutzen · kostenlose Konten können 1 hinzufügen · bei Team/Enterprise fügt ein Owner ihn hinzu

  1. Öffne die Connectors-Seite von Claude

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Klicke „Add“ → „Custom“ → „Web“ und fülle diese 2 Felder aus

    Kopiere jeden Wert in das gleichnamige Feld in Claude und klicke Continue

    Name · NameTennessee Code
    Remote MCP server URL · Adressehttps://gateway.pipeworx.io/tennessee-code/mcp

    Klicke auf der von Claude erkannten Anmelde-Seite auf Continue · wähle bei Authentication, was der Anbieter angibt (Sign in now, Sign in when needed oder No sign in), dann Add

  3. Im Chat einschalten

    +ConnectorsTennessee Code

  4. Ausprobieren

    Nutze Tennessee Code und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude sagt, dass es Tennessee Code nutzt, oder ein Werkzeug von Tennessee Code in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit ChatGPT je nach Tarif

Volles MCP: ChatGPT Business, Enterprise oder Edu im Web · Pro: verbindet mit Lese-/Abrufrechten, Werkzeuge, die Daten ändern, gehen evtl. nicht · Plus: in der Doku nicht bestätigt; siehst du auf der Plugins-Seite eine Option für eigene MCP-Server, kannst du es versuchen · nur Web

  1. In ChatGPT im Web die Seite zum Hinzufügen von MCP öffnen

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Name und Adresse eintragen

    Namen eingeben, Adresse unter Connection einfügen, Risikohinweis abhaken und Create as a plugin klicken

    Name · NameTennessee Code
    Connection · Adressehttps://gateway.pipeworx.io/tennessee-code/mcp
  3. Tennessee Code im Chat auswählen

    Neuen Chat öffnen und vor dem Tippen Tennessee Code aus deinen Plugins wählen

  4. Ausprobieren

    Nutze Tennessee Code und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn ChatGPT sagt, dass es Tennessee Code nutzt, oder ein Werkzeug von Tennessee Code in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von OpenAI abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Claude Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Terminal öffnen

    Mac: Command+Leertaste drücken und Terminal tippen · Windows: PowerShell öffnen

  2. Diesen Befehl einfügen und Enter drücken

    claude mcp add --transport http --scope user tennessee-code https://gateway.pipeworx.io/tennessee-code/mcp
  3. /mcp in Claude Code eingeben

    Tennessee Code sollte in der Liste als verbunden erscheinen

  4. Ausprobieren

    Nutze Tennessee Code und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Claude Code sagt, dass es Tennessee Code nutzt, oder ein Werkzeug von Tennessee Code in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Anthropic abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit Cursor · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button Cursor öffnen

    In Cursor öffnen

    Cursor fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in Cursor im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Tennessee Code und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn Cursor sagt, dass es Tennessee Code nutzt, oder ein Werkzeug von Tennessee Code in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von Cursor abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Klappt mit VS Code · etwa 2 Min.

Kein Schlüssel, nichts zu installieren

  1. Mit diesem Button VS Code öffnen

    In VS Code öffnen

    VS Code fragt nach einer Bestätigung; klicke Install

  2. KI-Chat in VS Code im Agent-Modus öffnen

  3. Ausprobieren

    Nutze Tennessee Code und sag mir, was du für mich tun kannst; zeig mir dann eine Sache

    ✓ Wenn VS Code sagt, dass es Tennessee Code nutzt, oder ein Werkzeug von Tennessee Code in der Antwort zeigt, bist du verbunden

Menünamen am 11. Nov. 2026 mit der Hilfe von VS Code abgeglichen · dein Bildschirm kann je nach App-Version leicht abweichen

Andere Apps mit MCP, etwa Windsurf, Zed oder Gemini CLI, fügen Server unterschiedlich hinzu. Sieh in der App-Liste nach

Alle Apps mit MCP ansehen →

Adresse für Apps, die über das Web verbinden

Adressehttps://gateway.pipeworx.io/tennessee-code/mcp

JSON-Einstellungen stehen unten unter „Für Entwickler“

Hängst du fest? Frag Leute, die Tennessee Code nutzen💬 Diskussion →
Für Entwickler: Terminal-Befehle und JSON-Einstellungen

Über das Web

Claude Code

claude mcp add --transport http --scope user tennessee-code https://gateway.pipeworx.io/tennessee-code/mcp

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

{
  "servers": {
    "tennessee-code": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/tennessee-code/mcp"
    }
  }
}

Auf deinem Computer installiert

Claude Code

claude mcp add --scope user tennessee-code -- npx -y @pipeworx/mcp-tennessee-code

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "tennessee-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "tennessee-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "tennessee-code": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-tennessee-code"
      ]
    }
  }
}

Werte, die du selbst einträgst

  • PIPEWORX_API_KEY geheim env
    Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Die Beschreibungen sind noch im englischen Original.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Auf einen Blick

Downloads pro Wochei
283/Wo.
Verbindung
Computer oder Cloud
Transport
stdio, streamable-http
Neueste Versioni
0.2.1
In der Registry veröffentlichti
6. Nov. 2026
Code zuletzt geänderti
9. Nov. 2026
Entwickler
pipeworx-io
Pakete
npm: @pipeworx/mcp-tennessee-code
Registry-Status
Aktiv

Welche Apps ihn nutzen können

Basierend darauf, wie sich dieser Server verbindet, und auf der eigenen Doku jeder App, geprüft am 10. Nov. 2026.

Verbinden sich über das Internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Laufen auf deinem Computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

Alle Apps, mit Vor- und Nachteilen →

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 12. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,231 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,231 across 1876 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1876 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CNPJ, or an LEI. Use this when you want

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • tn_statute

    Get a section of the Tennessee Code Annotated (T.C.A.) — Tennessee state law — by citation. "39-13-202" is first degree murder; "66-28-301" is the security-deposit statute. Accepts natural forms: "39-13-202", "T.C.A. 39-13-202", "Tenn. Code Ann. § 39-13-202". Returns the statutor

  • tn_search

    Search the Tennessee Code Annotated (T.C.A.) BY TOPIC or keyword rather than citation — "security deposit", "concealed carry", "DUI per se limit", "homicide". This matches OFFICIAL CATCHLINES/HEADINGS (e.g. "39-13-202. First degree murder." matches "murder"), not the full statuto

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 15. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto pipeworx-io bestätigt, dem das Repo gehört

  • ✓ Bestanden

    Wird noch gepflegt

    Code zuletzt geändert: vor 6 Tagen

  • ✓ Bestanden

    Hat eine Lizenz

    Nutzt MIT

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 64 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 46 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Veröffentlichte Schwachstellen (OSV.dev)

Noch nicht geprüft

Was wir prüfen → · JSON

Entwickler: neue Prüfung anfordern oder falsche Angaben melden

Diskussion

Fragen, Tipps teilen oder melden, dass etwas nicht geht. Sortiert nach „hilfreich“.

Noch keine Beiträge. Stell die erste Frage oder teile einen Tipp.

Beiträge hier stammen von Nutzern, nicht vom PopNx-Team.

Mit Google anmelden, um zu posten

Nutzerbewertungen

Noch keine Bewertungen

Mit Google anmelden, um zu bewerten

Im Vergleich mit anderen in Entwicklertoolsi

  • Mehr Sterne als 69 % der anderen 5909 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 71 % der anderen 5909 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 5909 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Tennessee Code sicher?

Er hat 5 von 5 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt vor 6 Tagen geändert, und die neueste Version (0.2.1) kam vor 9 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL und funktioniert daher auch in Apps mit Remote-MCP, etwa ChatGPT im Web (volles MCP ab Business; Pro nur lesend).

Was kann ich stattdessen nutzen?

In derselben Kategorie: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Ähnliche Alternativen

Gleiche Kategorie, andere Entwickler, Befehle bereits geprüft. Offizielle zuerst, dann nach Sternen.

So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

von ahmedkhaleel2004Weit verbreitet★ 18.919Aktualisiert vor 2 Monaten

Läuft in der Cloud✓ vom Dienst · gitdiagram.comVom PopNx-Team ausprobiert

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

von AppllamaWeit verbreitet★ 5174Aktualisiert vor 3 Monaten

Läuft in der Cloud✓ vom Dienst · appllama.io

Cloudflare MCP

Cloudflare MCP servers

von cloudflareWeit verbreitet★ 4466Aktualisiert vor 14 Monaten

Läuft in der Cloud✓ vom Dienst · mcp.cloudflare.comVom PopNx-Team ausprobiert

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

von omnara-aiWeit verbreitet★ 3395Aktualisiert vor 2 Monaten

Läuft in der Cloud✓ vom Dienst · omnara.com

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

von repowise-devWeit verbreitet↓ 6506/Wo.★ 8138 Sterne des ganzen ReposAktualisiert vorgestern

Computer oder Cloud✓ vom Dienst · repowise.dev
  • GitDiagram — Läuft in der Cloud, keine Installation · Kein Schlüssel nötig
  • Appllama — Läuft in der Cloud, keine Installation · Kein Schlüssel nötig
  • Cloudflare MCP — Läuft in der Cloud, keine Installation · Kein Schlüssel nötig · Im Verzeichnis von Claude
  • Omnara — Läuft in der Cloud, keine Installation · Kein Schlüssel nötig
  • Repowise — In der Cloud oder auf deinem Rechner · Kein Schlüssel nötig

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

@pipeworx/tennessee-code

Tennessee Code Annotated (T.C.A.) — state statutes by citation and by official catchline (topic search). Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

This pack serves a POINT-IN-TIME SNAPSHOT dated 2021-05-21, not the current code. Read "Why this is a snapshot" below before using it for anything where the exact current text matters — it says so on every response too.

Tools

  • tn_statute(citation) — full text of a T.C.A. section by citation ("39-13-202" is first degree murder; "66-28-301" is the security-deposit statute). Resolves the citation's title via a baked index, fetches that title's HTML live, and cuts the section out of it by its own unique anchor id. Also returns later_acts — every Public Chapter this pack's own home-built index shows touching this exact citation since the 2021-05-21 snapshot (fleet #2916, see "The overlay" below).
  • tn_search(query, limit?) — topic/keyword search over the baked citation + official-catchline index (not full statutory body text).

Auth

Keyless.

Why this is a snapshot, not the current code

Tennessee's own publishing arrangement routes the maintained, current TCA exclusively through LexisNexis's advance.lexis.com — a cookie/session-gated SPA with no stable per-citation URL, confirmed live (traced lexisnexis.com/hottopics/tncode -> advance.lexis.com/container?config=..., which immediately probes for cookie support and only then begins any client-side render). That is the same class of wall this pack family treats as OUT (ASP.NET postback / anti-bot / JS-rendered SPA).

There is no OTHER official electronic route, and that absence is litigated, not merely undocumented: Public.Resource.Org v. Matthew Bender & Co., 686 S.W.3d 1 (Tenn. Ct. App. 2023) (further appeal denied by the Tennessee Supreme Court, 2024), held that Tennessee's Public Records Act does not reach the electronic TCA, because LexisNexis is a private contractor performing services for the Code Commission under a separate statutory arrangement (T.C.A. § 1-2-114), not a state agency holding a public record. Having lost that fight — and having lost electronic access to the Code even before filing it — Public.Resource.Org had UniCourt scan and transform the print volumes, publishing the result at https://unicourt.github.io/cic-code-tn/:

"This repository was created by UniCourt on behalf of Public.Resource.Org.

All this work is in the public domain and there are NO RIGHTS RESERVED."

— Release 76, dated 2021.05.21.

That public-domain claim rests on the same "edict of government" theory the U.S. Supreme Court confirmed for Georgia's own annotated code in Georgia v. Public.Resource.Org, 590 U.S. 255 (2020) — and this is literally the same transform pipeline (cic-beautify-state-codes) and the same stylesheet reference this repo already trusts for mcps/georgia-code's upstream.

The same release is also uploaded to archive.org as item gov.tn.tca (byte-identical statutory text, verified directly). This pack calls the GitHub Pages copy instead, for two concrete reasons found during development, not a preference in the abstract:

  1. Reliability/latency. archive.org's mirror nodes answered this release with multiple transient HTTP 500s and multi-second-to-indefinite stalls while baking the index and smoke-testing tn_statute (a 7.2MB title took 12.9s on one call and simply never returned on another, even with a 60s client timeout and 3 retries). GitHub Pages was consistently sub-second for the same files, every time.
  2. Completeness. archive.org's own upload of Title 47 (Commercial Instruments and Transactions / UCC) carries a LexisNexis "© ... All rights reserved" notice and different markup entirely (p.p5) instead of PRO's public-domain transform (span.boldspan) that every other title there carries — evidently a bad upload of that one file. UniCourt's copy of Title 47 is the correct public-domain transform, like all 67 other titles. All 68 published titles are covered by this pack as a result (archive.org's copy would only support 66, with Title 47 and one other transient-failure title missing).

No newer release exists anywhere. Checked both the UniCourt index page's own "Release NN dated YYYY.MM.DD" listing and archive.org's separate upload: release 76 (2021.05.21) is the newest either has. The 2023-2024 litigation above is *why* — Public.Resource.Org was fighting to restore a current electronic feed and lost. So every response from this pack carries current_through and data_as_of stating 2021-05-21 explicitly. Roughly five Tennessee legislative sessions (2021-2025) of amendments are NOT reflected.

Other free routes were checked and ruled out, not merely skipped:

CandidateResult
wapp.capitol.tn.gov / capitol.tn.gov (TN General Assembly)Publishes Public Chapters (session laws as passed) and bill text, but no consolidated current code — its own "Tennessee Code" link routes to the same LexisNexis wall above. Session laws are a DIFFERENT document from the codified TCA (see "Public Chapters are not the Code" below).
law.justia.com/codes/tennessee/Serves Cloudflare's "Just a moment" managed JS challenge (HTTP 403, cf_chl_opt present) to a bare fetch — not a bypassable bare-UA gate, the same bot-wall class this pack family treats as OUT. Google's own crawler evidently gets through (indexed pages appear in search), a plain HTTP client does not.
codes.findlaw.com/tn/Same Cloudflare managed challenge, same result.
law.resource.org/pub/us/code/tn/This is the litigation docket for the lawsuit above (court filings, 2021-2024), not a code mirror. The actual scanned text lives in the two mirrors above, not on law.resource.org's own file tree.
SOS (sos.tn.gov)Publishes Acts and Resolutions (session laws), not a consolidated code; it directs electronic TCA requests to LexisNexis per the Code Commission's arrangement.
Public Chapters are not the Code

Tennessee's General Assembly publishes Public Chapters — the session laws as enacted, year by year, e.g. capitol.tn.gov/Archives/Joint/publications/PublicChapters/2024/... — and these ARE current and free. But a Public Chapter is an amending instrument ("AN ACT to amend Tennessee Code Annotated, Title 47...") , not the codified text itself — reading one tells you a change happened, not what the amended section now reads as a whole next to the rest of the code. This pack does not attempt to fold session laws into the frozen 2021-05-21 text (that reconciliation is exactly what a Code Commission codification does, and is out of scope here) — it would be dishonest to call that composite "the current code" without doing the actual reconciliation work. If a caller needs what changed since 2021, they need the Public Chapters directly, not this pack.

The overlay: later acts, never merged (fleet #2916)

Bruce kept tn_statute on the frozen 2021-05-21 snapshot ("figure something out") rather than chase a fully reconciled current code — same call as Arkansas (fleet #2906) and Mississippi (fleet #2915). This overlay is the cheapest honest improvement on top of that decision — design and measurements in docs/current-statute-routes.md (#2902).

The rule: never rewrite the snapshot `text`. Only ever ADD a dated, linked list beside it, explicitly labelled as not merged. tn_statute's response carries:

  • later_acts — one entry per Public Chapter that touched this exact citation since the snapshot date: public_chapter (number), general_assembly (e.g. "114"), bill (e.g. "HB0001"), link (the bill's own PDF), verb ("amended" / "repealed" / "new_section"), source: "tnga", merged: false. Empty ([]) means this pack's own index shows no later Public Chapter for this citation across every Effective Report checked — not that the overlay failed to load (a missing/malformed baked index throws loudly instead, same as tn_search's catchline index).
  • sessions_checked — every Public Chapters Effective Report the index covers, named even when later_acts is empty, so a caller can tell "nothing changed" from "we didn't check."
  • later_acts_data_as_of — when the overlay was last baked.
  • later_acts_parse_rate_pct — the measured share of "Tennessee Code Annotated, Section/Title ..." amendment clauses the baker could actually resolve to a citation, across every bill PDF it fetched for this bake (see "Measured coverage" below). date: null on every act entry, honestly — neither the Effective Report nor the bill PDF gives a per-citation enactment date (the Effective Report's date is per-chapter, not per-section); guessing one would be worse than saying so.

Source, and why it is HOME-BUILT rather than a state-maintained index (unlike Arkansas): Tennessee's legislature publishes no "citation touched by this act" index the way arkleg.state.ar.us does — confirmed by docs/current-statute-routes.md. This pack builds the index itself from two keyless public sources, both confirmed live with no bot wall and no login:

  1. Which bills became law, and their Public Chapter number — the Tennessee General Assembly's own "Public Chapters Effective Report" (capitol.tn.gov/Archives/Joint/publications/PublicChapters/ / PublicChapters_ <01|07>.pdf), published twice a year. A plain, keyless, text-extractable PDF table of every bill that became a Public Chapter that General Assembly, with its PC number and effective date(s) — but only a Title/Chapter-level abstract, not exact section citations.
  2. The exact citation touched — each enacted bill's own text, served keylessly at capitol.tn.gov/Bills/ /Bill/ .pdf, parsed for the fixed boilerplate "Tennessee Code Annotated, Section , is amended ..." (also "... is repealed ..." and, for a wholly new section, "... Title X, Chapter Y[, Part Z], is amended by adding the following as a new part/section:" followed by the new section's own numbered heading).

Known, stated limit: the linked bill text is AS-FILED, not a separately published AS-ENACTED document. Tennessee does not host a stable keyless URL for the signed, final text the way Arkansas's index links straight to the Act PDF — the one source that would carry it, the Secretary of State's "Acts and Resolutions" page (sos.tn.gov), answers this pack's honest User-Agent with an HTTP 403 from a CloudFront/WAF rule (confirmed live, 2026-10-09) while a browser UA passes; this pack does not spoof a UA to get through that wall. So a later_acts entry is a reliable signal that *this citation was touched by this Public Chapter*, linked to the bill's own filed text — not a guarantee that text is byte-identical to the final floor-amended language.

Discovery, not hardcoding: the set of Effective Reports to check is read live from wapp.capitol.tn.gov/apps/WebPublications/Index's own publications table, so a newly published report shows up with no code change — same self-extension property as Arkansas's -driven session discovery.

A section not found in the Release-76 snapshot but present in the overlay is flagged specially: tn_statute's found: false response carries later_acts_if_created — if the index shows Public Chapters against a citation that does not exist in the 2021 snapshot, that is a signal the section may have been CREATED after the snapshot date, not necessarily a bad citation.

Measured coverage (fleet #2916 bake, captured 2026-10-10)
  • 11 Effective Reports checked (July 2021 through July 2026), covering the **112th, 113th, and 114th General Assemblie

Nur der Anfang wird gezeigt; den Rest findest du im Repo