Skip to content

TEOS Intelligence MCP server

Which MCP servers are TEOS Intelligence's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-25

← Back to TEOS Intelligence

Whose server it is
  • Registry namecom.tppflow/texas-rrc-wellboresverified in the MCP registry

The registry name sits under tppflow.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-25
  • Stateanswerschecked 2026-10-25
  • Tools2
  • Server calls itselfteos-rrc
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 505 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: query layoff notices by state through an API; build lead lists of companies with mass layoffs.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-25
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer519 ms
  • Space in an agent's context≈ 722 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 2 of 2

What an agent can do with it

  • cannot · query layoff notices by state through an API
  • cannot · build lead lists of companies with mass layoffs
  • not sure · gather layoff evidence for employment litigation

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-25
  • describe_texas_wellbores

    Free, no API key required. Describes the Texas Railroad Commission wellbore identity dataset decoded from RRC's EBCDIC mainframe corpus: the exact fields available, row count, freshness, pricing, and which parts of the source are NOT yet…

  • search_texas_wellbores

    Search Texas oil and gas wellbore identities by district, county, API number, plugged status, orphan-well hold, completion date range or minimum depth. FREE tier: up to 25 real decoded rows per call with no API key, so you can judge the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "texas-rrc-wellbores": {
      "type": "http",
      "url": "https://mcp.tppflow.com/rrc"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http tppflow https://mcp.tppflow.com/rrc

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.tppflow.com/rrc as a custom connector in the settings.

Other servers listed as TEOS Intelligence's
  • com.tppflow/warn-act-layoffsanswers, 3 toolsverified in the MCP registry

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.