fixRAgent maintenance triage
REMOTE · FIXRAGENT.COM · SCANNED SEP 27
Assess a property maintenance photo: what it is, how urgent, which trade to call.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1163 tokens (~387/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the fixRAgent maintenance triage MCP server?
fixRAgent maintenance triage is a hosted endpoint at https://fixragent.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · fixragent.com
claude mcp add --transport http russ4102-fixragent 'https://fixragent.com/mcp'
{
"mcpServers": {
"russ4102-fixragent": {
"url": "https://fixragent.com/mcp"
}
}
} {
"servers": {
"russ4102-fixragent": {
"type": "http",
"url": "https://fixragent.com/mcp"
}
}
} [mcp_servers.russ4102-fixragent] url = "https://fixragent.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"russ4102-fixragent": {
"type": "remote",
"url": "https://fixragent.com/mcp",
"enabled": true
}
}
} openclaw mcp add russ4102-fixragent --url 'https://fixragent.com/mcp' --transport streamable-http
mcp_servers:
russ4102-fixragent:
url: "https://fixragent.com/mcp" {
"McpServers": {
"russ4102-fixragent": {
"Transport": "http",
"Url": "https://fixragent.com/mcp"
}
}
} assistant mcp add russ4102-fixragent -t streamable-http -u 'https://fixragent.com/mcp'
{
"mcpServers": {
"russ4102-fixragent": {
"type": "http",
"url": "https://fixragent.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://fixragent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fixragent.com | CN=YR2,O=Let's Encrypt,C=US | 16 Aug 2026 | 14 Nov 2026 | RSA 2048 | SHA256-RSA | 63b46fc3cdb6e071679cb2b2c1ef968a794 |
| SANs: fixragent.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fixragent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fixragent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), serial=(), hid=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fixragent.com/mcp | Verified | 200 | |
| http (plaintext) | http://fixragent.com/mcp | HTTPS enforced | 308 | https://fixragent.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_property_photo Assess a property maintenance photo ~579
Use this when someone has 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 wants to know what it is, how urgent it is, and which trade to call. Typical asks: "what is wrong with this water heater", "my tenant sent this photo, is it urgent", "which trade do I call for this". 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 does not read the photo: it returns fixRAgent's stored sample result, labelled SAMPLE, and says how to get a free key. Do not use this for: a person, a pet, an injury, a rash, a medical or veterinary question, a vehicle, food, a document, a screenshot, or a photo of a screen. Do not use it for anything happening RIGHT NOW that needs emergency services — a fire, a gas smell or hissing gas, a carbon-monoxide alarm sounding, water pouring onto live electrics, or anyone hurt: tell the user to leave the building and call 911 (or the local emergency number) first, and do not call this tool. Do not use it to price a repair, to book a contractor, or to decide an insurance claim; it routes the job, it does not quote or dispatch it.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | fast reads the photo three times, deep five, and the reply reports how many agreed. deep is slower and spends more of the day's budget; use it only when a first read disagreed with itself. |
| image_base64 | string | yes | The photo, base64-encoded. A data:image/jpeg;base64, prefix is accepted and stripped. JPEG, PNG or WebP, at most 3 MB once decoded, at least 1 KB. Location metadata is removed on our server before th… |
| mime_type | string | yes | The photo's type. Must match the bytes; a mismatch is refused, not guessed. |
| problem_text | string | – | What the person reported, in their own words ("no hot water since Tuesday"). Optional. Treated as a reported symptom to be checked against the photo, never as ground truth: the reply says whether the… |
| reporter | string | – | Who took the photo. Changes how the explanation is worded, not the verdict. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | – | – | n reads ran, k agreed. k is null on a tie. |
| config_id | string | – | An id beginning "fallback-" means a hardcoded config answered, not a measured one. |
| core | object | yes | The fixed contract: asset, fault, tier, trade_required, resident_explanation and the rest. |
| diagnosis_id | string | yes | Server-minted id for this assessment; the key for the profile and the outcome. |
| engine_version | string | – | – |
| outcome_url | string | – | Two taps to tell us what actually fixed it. |
| rubric_version | string | – | – |
| sample | boolean | – | true = no key was sent: this is the stored SAMPLE, NOT an assessment of the photo you sent. Absent on a real assessment. |
| share_url | string | yes | The Triage Profile as a page a resident or contractor can open. |
| warnings | array | – | – |
No examples provided.
get_triage_profile Read back a saved triage profile ~162
Use this when you already have a fixRAgent diagnosis_id (from assess_property_photo, or from a fixragent.com/c/<id> link a person pasted) and want the saved assessment back as data. Reads only; it never re-reads the photo, never calls the model, and spends nothing from the daily allowance. Do not use this to assess a new photo — that is assess_property_photo. Do not use it to look up a person, an address, a property or an account: it takes one id and returns one assessment, and it returns no contact details of any kind.
| Name | Type | Req | Description |
|---|---|---|---|
| diagnosis_id | string | yes | The UUID from assess_property_photo, or the last path segment of a fixragent.com/c/<id> link. |
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | – | – | – |
| config_id | – | – | – |
| core | object | yes | – |
| created_at | – | – | – |
| diagnosis_id | string | yes | – |
| engine_version | – | – | – |
| rubric_version | – | – | – |
| share_url | string | yes | – |
No examples provided.
try_sample Try a sample assessment (no key needed) ~124
Use this FIRST when the person has just connected fixRAgent, has no key yet, or asks what fixRAgent does or what a result looks like. It needs no key, takes no input, and returns a real 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. It does not read any photo and spends nothing. Do not present the sample as an assessment of the person's own photo; for their photo, use assess_property_photo with a key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | – | – | n reads ran, k agreed. |
| captured_utc | string | – | When the real engine produced this answer. |
| config_id | string | – | – |
| core | object | yes | The fixed contract, exactly as the engine returned it for the sample photo. |
| diagnosis_id | string | – | – |
| engine_version | string | – | – |
| label | string | yes | One sentence saying what this is, to show the person as-is. |
| next_step | string | yes | How to get a free key and assess your own photo. |
| photo | object | – | What the sample photo shows, in words. The photo itself is not served. |
| rubric_version | string | – | – |
| sample | boolean | yes | Always true: this is a stored example, not a read of any photo you sent. |
No examples provided.
What is the fixRAgent maintenance triage MCP server?
fixRAgent maintenance triage is an MCP server listed in the public MCP registry as io.github.Russ4102/fixragent. Assess a property maintenance photo: what it is, how urgent, which trade to call. This page covers its hosted endpoint (https://fixragent.com/mcp).
Is the fixRAgent maintenance triage MCP server safe to use?
fixRAgent maintenance triage scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the fixRAgent maintenance triage MCP server expose?
fixRAgent maintenance triage exposes 3 tools: assess_property_photo, get_triage_profile, try_sample. Their descriptions and schemas cost roughly 865 tokens of context every time the server is loaded.
Does the fixRAgent maintenance triage MCP server require authentication?
No. We connected to fixRAgent maintenance triage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the fixRAgent maintenance triage MCP server still maintained?
fixRAgent maintenance triage is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.