Other · Remote MCP server
Sighttrue
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.kaitzyy-dev/sighttrue- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- kaitzyy-dev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/kaitzyy-dev) · how
- Website
- sighttrue.com
- Repository
- github.com/kaitzyy-dev/sighttrue
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://sighttrue.com/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- sighttrue 1.0.0 · protocol 2025-06-18
- Tools discovered
31 - show names
check_before_install,check_package,check_stack,search_repositories,compare_repositories,find_model,check_eol,check_provider,list_readings,who_can_publish,package_weight_history,withdrawn_but_installed,typosquat_check,funding_gap,time_to_fix,advisory_severity,runtime_deadlines,base_image_check,registry_health,provider_incidents,provider_transparency,provider_terms_changed,model_price_history,model_withdrawn,help_availability,audit_manifest,diff_since,watch_add,watch_changes,explain_finding,domain_risk- Checked on
- 2026-10-05
How to connect Sighttrue
Sighttrue is a remote MCP server: there is nothing to install. Its endpoint is https://sighttrue.com/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| SidereonGNSS positioning and astrodynamics: orbit propagation, passes, GNSS solves, and RINEX QC. | Local · stdio |
| Sieve MCPAI startup due diligence - screen companies across 7 dimensions, get a Sieve Score. | Local · stdio |
| siftRuns a command, keeps every byte on disk, returns only the lines that matter. | Local · stdio |
| Sigasi Magic HDLAnalyze and verify Verilog, SystemVerilog, and VHDL projects from AI agents over MCP. | Local · stdio |
| SigilLocal keystore + MCP server. Claude can sign EVM transactions but never sees the private key. | Local · stdio |
| SignageSpaceManage digital signage screens, playlists and media from your AI assistant. | Remote · HTTPLive check: sign-in required |
| Signal BureauSigB (Signal Bureau): maintained, source-traced record of entities and events in your named domain. | Remote · HTTPLive check: ✓ handshake |
| Signal-One by EMETZORVerified external-state intelligence for agents with corroborated evidence and ANSWER or WAIT. | Remote · HTTPLive check: ✗ no handshake |