fixRAgent maintenance triage is listed as active in the registry but did not answer our last check. It exposes 3 tools.
Assess a property maintenance photo: what it is, how urgent, which trade to call.
Uptime history
42 days of history · worst day 0%
42 days agonow
14.3%
Uptime 24h
13 of 91 checks
3
Tools
read from the server
334 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 12
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.
18 Oct
2 tool descriptions were rewritten
assess_property_photo, get_triage_profile
18 Oct
2 tools changed the parameters they ask for
assess_property_photo, get_triage_profile
9 Oct
a tool description was rewritten
get_triage_profile
9 Oct
a tool changed version
7 Oct
a tool description was rewritten
get_triage_profile
30 Sep
3 tool descriptions were rewritten
assess_property_photo, get_triage_profile, try_sample
30 Sep
2 tools changed the parameters they ask for
assess_property_photo, get_triage_profile
fixRAgent maintenance triage does not always answer
Over the last week it answered 4.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
run in your terminal
claude mcp add fixragent --transport http https://fixragent.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://fixragent.com/mcp~/.codex/config.toml
[mcp_servers.fixragent]
url = "https://fixragent.com/mcp".cursor/mcp.json
{
"mcpServers": {
"fixragent": {
"url": "https://fixragent.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"fixragent": {
"type": "http",
"url": "https://fixragent.com/mcp"
}
}
}Available tools 3
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
assess
assess_property_photo
Assesses a photo of something in a building — an appliance, a boiler, a pipe, a water heater, an electrical panel, a fitting, a leak, damage — and reports what it is, how urgent it is and which trade it needs. Returns the fixed contract: what the asset is, whether a fault is visible, one of four urgency words (EMERGENCY, TODAY, THIS WEEK, WHENEVER), which trade to call, a line to say to the resident, and how many independent reads agreed. One call reads the photo on fixragent.com and spends one request from the key's daily allowance. Sent with NO key, it reads the real photo up to 3 times per connection in a rolling 24 hours (a small free allowance, shared across every keyless caller up to a daily ceiling); past either limit it returns fixRAgent's stored sample result, labelled SAMPLE, and says how to get a free key with no such limit. It reads only a real photo: a written description is not a photo and is not assessed. With no photo, or a photo it cannot read, nothing is assessed and the reply gives a fixragent.com link where the person adds the photo and sees the full Triage Profile. An urgency, trade or finding that this call did not return is not fixRAgent's. Scope: photos of building assets and faults. It does not assess people, pets, injuries, rashes, medical or veterinary questions, vehicles, food, documents, screenshots or photos of screens. It is not an emergency service: a fire, a gas smell or hissing gas, a carbon-monoxide alarm sounding, water pouring onto live electrics or anyone hurt needs the local emergency number (911 in the US), not a photo assessment. It does not price repairs, book contractors or decide insurance claims; it routes the job, it does not quote or dispatch it.
triage
get_triage_profile
Returns a saved fixRAgent assessment by its diagnosis_id (from an assessment, the last part of a fixragent.com/c/<id> link, or the h- code that comes with a fixragent.com photo link once the photo has been added there; with no photo added yet, it reports that there is no result). Read only: it never re-reads the photo, never calls the model and spends nothing from the daily allowance. It takes one id and returns one assessment with no contact details of any kind, the same assessment anyone with its fixragent.com/c/ link can open. It needs no key; if a key is sent, it must be a valid one. Reads are limited to 20 an hour per address, shared with assessments.
try
try_sample
Returns a stored fixRAgent assessment of a sample photo from fixRAgent's test set (an HVAC air handler and furnace), labelled SAMPLE, plus how to get a free key. Needs no key and no input, reads no photo and spends nothing. The result is a sample, not an assessment of anyone's own photo.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://fixragent.com/mcp | streamable-http | answering | 111 ms | 11 min ago |
Alternatives to fixRAgent maintenance triage
same job, measured the same wayZabbix AI CLI MCP
by stufently
Task-shaped Zabbix access for AI agents: problems, host triage, metrics, maintenance windows.
Eclipse Feedforge
by cyan-eclipse-technologies-llc
Messy catalog to agent-grade feed with per-attribute provenance. LOCAL/fixture only.
Patent Maintenance Fees
by pipeworx-io
USPTO Patent Maintenance Fee Events — complements the `patents` pack (fleet #3258), which has…
Trakis SEO checks
by trakis
66 technical SEO and AI-readiness checks: what each looks at, why it matters, how to fix it
U
Upright
by blueveta
Detects whether a product photo is upright and how many degrees to rotate it.
PropSWOT — Property Management AI
by tapads
Property management AI: work orders, vendors, appliances, and triage for Claude and ChatGPT.
Starlog
by starloghq
Vet a package (CVEs, license, maintenance) before your AI agent uses it, plus capability discovery.
gut
by kungie
Judgment calls on small, cheap models: is this spam, which team, how urgent. YES, NO or UNSURE.
fixRAgent maintenance triage — questions
Answers built from our own checks of this server.
What can fixRAgent maintenance triage do?
It exposes 3 tools, read directly from the server on our last check. Among them: assess_property_photo, get_triage_profile, try_sample. 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 →
Is fixRAgent maintenance triage working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 13 of 91 checks got a reply (14.3%), average response time 334 ms. The bar chart above shows every period we have measured.
The registry lists fixRAgent maintenance triage as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect fixRAgent maintenance triage?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does fixRAgent maintenance triage need an API key?
No. fixRAgent maintenance triage completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is fixRAgent maintenance triage?
It answers our handshake in 334 ms on average, which is faster than 42% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.