Index / MCP servers / io.github.CHANGCHINFU/mcp-gauge

io.github.CHANGCHINFU/mcp-gauge MCP server

Connect io.github.CHANGCHINFU/mcp-gauge and your agent gets 5 tools, among them find_signal, get_official_record, purchase_options. It answers at https://api.truthbear.co/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 19 October 2026, succeeded.

Status
Answering
Tools
5
Reliability
6 of 6 checks
Response time
826 ms
Transport
streamable HTTP
Last checked
19 October 2026

Verify official facts with Bitcoin-anchored proof. 180+ signals, x402 pay-per-call.

Description as the publisher wrote it.

The 5 tools io.github.CHANGCHINFU/mcp-gauge offers

ToolWhat it does
find_signalFREE coverage + freshness manifest: which signal_id lines exist, how many entities each covers, and fresh/recent/stale counts - so you can check "is my entity covered and how fresh" BEFORE paying. Optional filters: industry, signal_id, enti
Inputs: industry, signal_id, entity, full
get_official_recordReturns the REAL x402 payment challenge (accepts[]: network / asset / payTo / amount) for the paid endpoint that serves a given signal_id+entity, or any listed endpoint addressed directly by `path`. This tool does NOT deliver paid data and
Inputs: path, signal_id, entity, dim
purchase_optionsFREE. Ask how to pay for a listed endpoint and get every channel with its REAL status - including the ones that are wired but not open yet. Three channels exist: x402 micropayment (for an agent with a funded USDC wallet on Base), a stateles
Inputs: path
verify_citationFREE. Given a record_hash from any Truth Bear record, look it up and recompute the canonical hash server-side, returning whether it is a genuine Truth Bear official record plus a plain-language reverse lookup of what exactly that hash attes
Inputs: record_hash
verify_triangularFREE. Cross-verify one GAUGE interweave line: it returns each official series ("leg") in the line with its own record_hash, current/previous values, expected direction and per-leg minMove deadband, plus a count-style state (directions_match
Inputs: line, entity

Add io.github.CHANGCHINFU/mcp-gauge to your AI client

Every block below points at https://api.truthbear.co/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http io-github-changchinfu-mcp-gauge https://api.truthbear.co/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.truthbear.co/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "io-github-changchinfu-mcp-gauge": {
      "type": "http",
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "io-github-changchinfu-mcp-gauge": {
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "serverUrl": "https://api.truthbear.co/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: io.github.CHANGCHINFU/mcp-gauge
version: 0.0.1
schema: v1
mcpServers:
  - name: io.github.CHANGCHINFU/mcp-gauge
    type: streamable-http
    url: https://api.truthbear.co/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "httpUrl": "https://api.truthbear.co/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "type": "http",
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "io-github-changchinfu-mcp-gauge": {
      "url": "https://api.truthbear.co/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fapi.truthbear.co%2Fmcp&type=streamable_http&id=io-github-changchinfu-mcp-gauge&name=io.github.CHANGCHINFU/mcp-gauge

Is io.github.CHANGCHINFU/mcp-gauge up right now?

It answered our last check on 19 October 2026 in 826 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to io.github.CHANGCHINFU/mcp-gauge

Questions about io.github.CHANGCHINFU/mcp-gauge

How many tools does io.github.CHANGCHINFU/mcp-gauge have?

5, as returned by the server's own tools/list on 12 September 2026: find_signal, get_official_record, purchase_options, verify_citation, verify_triangular.

Is io.github.CHANGCHINFU/mcp-gauge down?

It answered our last check on 19 October 2026 in 826 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add io.github.CHANGCHINFU/mcp-gauge to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.truthbear.co/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does io.github.CHANGCHINFU/mcp-gauge need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.changchinfu. Endpoint host: api.truthbear.co. ARD identifier: urn:air:io.github.changchinfu:mcp:mcp-gauge. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.