Sighttrue is answering right now. Last checked 1 min ago. It exposes 31 tools. Last commit 1 Sep 2026.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
Uptime history
25 days of history
25 days agonow
100.0%
Uptime 24h
92 of 92 checks
31
Tools
read from the server
171 ms
Response time
average over 24h
1
Stars
last commit 1 Sep 2026
What the code does
We read the source, 12 h ago · tools taken from the live server · rules 3dff92dd89df
Capabilities
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
Page executes code built at runtime
assets/brand/launch.html:149
stage.innerHTML =
// x402 is spelled with a lowercase x. The eyebrow uppercases its contents
// and turned the protocol's name into something that is not its name.
line('<span class="eyebrow">Pay per call — <span style="text-transform:none">x402</span>…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add sighttrue --transport http https://sighttrue.com/api/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"sighttrue": {
"url": "https://sighttrue.com/api/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.sighttrue]
url = "https://sighttrue.com/api/mcp".cursor/mcp.json
{
"mcpServers": {
"sighttrue": {
"url": "https://sighttrue.com/api/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"sighttrue": {
"url": "https://sighttrue.com/api/mcp"
}
}
}Available tools 31
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
provider
check_provider
Recorded incidents for a hosting or API provider over a window, kept after the provider’s own status page dropped them.
provider_incidents
A provider’s recorded incidents, grouped by the component that failed, over the whole archive rather than the window its status page shows. Requires a key; see https://sighttrue.com/pricing.
provider_terms_changed
When a provider last changed its terms or pricing page, from a stored fingerprint of the page. Requires a key; see https://sighttrue.com/pricing.
provider_transparency
How long a provider takes to acknowledge an incident: the interval between an incident starting and its first public update. Requires a key; see https://sighttrue.com/pricing.
model
find_model
Find language models by price and context window, from a catalogue read daily across sixty providers. Use this before choosing a model: prices move without announcement and training data is out of date on the day it ships.
model_price_history
Every recorded price for a model, with the date each was read. Requires a key; see https://sighttrue.com/pricing.
model_withdrawn
Models that were in the catalogue and no longer are, with the date last seen. Requires a key; see https://sighttrue.com/pricing.
package
check_package
Read the current standing of one open-source package: downloads with the window they cover, OpenSSF scorecard, advisory count, licence, whether the repository is archived, and when it was last pushed to.
package_weight_history
How the published artefact size has moved over time. Returns the readings taken, not a verdict. Requires a key; see https://sighttrue.com/pricing.
watch
watch_add
Add a package to the caller’s own private watchlist, so later readings are about their stack rather than the public one. The list is private to the key that created it. Requires a key; see https://sighttrue.com/pricing.
watch_changes
Everything that has changed across the caller’s private watchlist since a given date: withdrawals, licence changes, advisories, archived repositories and runtimes going out of support. Requires a key; see https://sighttrue.com/pricing.
advisory
advisory_severity
Advisories broken down by severity rather than counted, with identifiers and dates. Requires a key; see https://sighttrue.com/pricing.
audit
audit_manifest
Read a whole manifest and return every reading on record for it, ordered by how much a reviewer would want to know. One call instead of one per dependency. Requires a key; see https://sighttrue.com/pricing.
base
base_image_check
For a container base image: its size, when it was last rebuilt, and whether the OS underneath it is still supported. Requires a key; see https://sighttrue.com/pricing.
before
check_before_install
Call this before adding a dependency. Returns only the facts a reviewer would be annoyed to discover afterwards: whether the publisher has withdrawn the package, whether it runs scripts on the installing machine, whether its repository is archived, how many advisories are on record, whether the licence is source-available, and how long since it was actually published. Each fact carries the address of the body that published it. It does not say whether to install; it says what is on record.
compare
compare_repositories
Hold two watched repositories against each other across downloads, OpenSSF scorecard, advisories, forks, stars and findings on record. Compares only; it does not pick a winner.
diff
diff_since
What changed for a set of packages since a given date, read from the daily archive. Requires a key; see https://sighttrue.com/pricing.
domain
domain_risk
Whether the domains a package points at — homepage, funding, documentation — still resolve to a registered owner. Requires a key; see https://sighttrue.com/pricing.
eol
check_eol
Check whether a runtime, database or framework release is still receiving security fixes, and what to move to. Covers about two dozen products read daily from endoflife.date.
explain
explain_finding
Given a finding id, return what was measured, when, by whom, and the address it can be checked at. For an agent quoting a figure into a review. Requires a key; see https://sighttrue.com/pricing.
funding
funding_gap
Packages that ask for funding, beside how heavily they are installed and how many people write them. Requires a key; see https://sighttrue.com/pricing.
help
help_availability
For a technology tag: questions asked against questions answered, over time. Requires a key; see https://sighttrue.com/pricing.
readings
list_readings
List every reading this server can return, what each one measures, and which require a key. Call this first if unsure which tool answers a question.
registry
registry_health
Recorded outages of the package registries themselves, kept after their status pages drop them. Requires a key; see https://sighttrue.com/pricing.
repositories
search_repositories
Find watched repositories whose name contains a string, with their current readings. Use it to discover what is covered before calling the other tools.
runtime
runtime_deadlines
Support end dates for the runtimes a dependency set requires, including any already past. Requires a key; see https://sighttrue.com/pricing.
stack
check_stack
Read a whole dependency list at once and report what is archived, what carries advisories, what has a source-available licence, and what has not been pushed to in a year. Use when reviewing a package.json, requirements.txt, Cargo.toml, composer.json or Gemfile.
time
time_to_fix
Days between an advisory being published and a release appearing that postdates it, per package and as a distribution. Requires a key; see https://sighttrue.com/pricing.
typosquat
typosquat_check
Whether a name is one edit away from a more widely installed package. States that both names exist; which one was meant is the caller’s call. Requires a key; see https://sighttrue.com/pricing.
who
who_can_publish
How many accounts hold publish rights on a package, as the registry lists them. Answers who can put code on your machine, which is a different question from who writes it. Requires a key; see https://sighttrue.com/pricing.
withdrawn
withdrawn_but_installed
Packages whose own publisher has withdrawn them and which are still being installed heavily, with the download figure and the publisher’s notice. Requires a key; see https://sighttrue.com/pricing.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://sighttrue.com/api/mcp | streamable-http | answering | 183 ms | 1 min ago |
Alternatives to Sighttrue
same job, measured the same wayUptimebolt MCP Server
by clm-cloud-solutions
AI-powered infrastructure monitoring — health, incidents, predictions, RCA, deploy safety
Superlog
by superlog
Open-source agent that observes and fixes your application. Query logs, traces, metrics, incidents.
YAPL
by yapl
Draft-safe project planning: tasks, dependencies, resources, schedules and cost metrics.
Jaeger MCP
by mshegolev
Jaeger MCP — search traces, inspect spans, map service dependencies (read-only).
GSA Per Diem
by 1102tools
GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools.
Model Ledger
by block
Model inventory and governance: trace deployed models and their dependencies as an append-only log
GCP Platform Engineer
by debilla
Read-only GCP tools for debugging incidents and finding cost savings
Health Export MCP
by philipad
Query 190 Apple Health metrics from any MCP agent: zero-dependency, read-only, local-first.
Sighttrue — questions
Answers built from our own checks of this server.
What can Sighttrue do?
It exposes 31 tools, read directly from the server on our last check. Among them: advisory_severity, audit_manifest, base_image_check, check_before_install, check_eol, check_package and 25 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Sighttrue mostly used for?
Its tools cluster around provider, model and package. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Sighttrue working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 171 ms. The bar chart above shows every period we have measured.
How do I connect Sighttrue?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sighttrue need an API key?
No. Sighttrue completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 31 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Sighttrue?
It answers our handshake in 171 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Sighttrue open source?
Yes — it is published under the MIT licence, written in TypeScript, 1 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.