Skip to content

MCP servers › com.andarehomes › tools

MCP server · registry snapshot 2026-11-17 · last tested 2026-11-17

tools MCP server

Registry name com.andarehomes/tools

Andare Homes Tools — the publisher's title

by andarehomes.com · domain (the registry's namespace rule)

Planning calculators for custom homes, additions and major renovations. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-17version 1.0.0streamable HTTP11 tools

Summary

com.andarehomes/tools is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain andarehomes.com. On 2026-11-17 ProtocolProbe connected to it in read-only mode and read its inventory: 11 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
11
Last tested
2026-11-17

Tool list size

7,025 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (11 tools). Counted with Anthropic's token counter on 2026-11-17, from the tool list we read on 2026-11-17. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-17 (andarehomes.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-17
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 1.0.0 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

What does this server offer?

Observed inventory
11tools
0resources
0prompts

None of its 11 tools are described as changing anything. For 11 the reading was uncertain, so no mark is shown.

  • toronto-building-permit-checker

    “Says whether a project in Toronto needs a building permit, usually does not, or depends, with the City source for the answer.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    18 inputs, 1 required
    • projectstringrequired“What is being built”
    • suitestring“basement: Will the work create a second suite or any additional dwelling unit?”
    • structstring“basement: Will it include structural or material alterations, such as adding or removing walls, excavation, underpinning or a new basement entrance?”
    • mechstring“basement: Will it include new plumbing or heating work?”
    • hstring“deck: How high will the finished deck level be above the adjacent finished grade?”
    • attstring“deck: Will the deck be attached to the house?”
    • exitstring“deck: Will it have a roof, or will it be part of a required exit from the house?”
    • lbstring“wall: Is the wall load bearing?”
    • kindstring“opening: What is the work?”
    • btstring“opening: What kind of building is it?”
    • chgstring“opening: Will the work affect the structural support or create a new exit?”
    • plumbstring“kitchen: Will you add or move plumbing, such as relocating a sink, shower, tub, toilet or drain?”
    • wallsstring“kitchen: Will you add or remove any walls or change any openings?”
    • scopestring“kitchen: Is the work limited to replacing cabinets, counters, finishes and fixtures in the same locations?”
    • sizestring“shed: What is the gross floor area?”
    • poolstring“fence: Is the fence a swimming pool enclosure?”
    • wherestring“fence: Where will the fence be?”
    • htstring“fence: How tall will it be?”
  • garden-suite-zoning-checker

    “Checks height, separation, floor area, setbacks and lot coverage of a garden suite against Toronto By-law 849-2025.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    16 inputs, 16 required
    • zonestringrequired“Property is in a residential zone (R, RD, RS, RT, RM)”
    • lanewaystringrequired“Property abuts a public laneway”
    • lot_areanumberrequired“Lot area (m2)”
    • lot_depthnumberrequired“Lot depth (m)”
    • lot_frontagenumberrequired“Lot frontage (m)”
    • house_gfanumberrequired“House gross floor area, all floors (m2)”
    • house_footprintnumberrequired“House footprint (m2)”
    • ancillary_footprintnumberrequired“Footprint of all ancillary buildings together, including the suite (m2)”
    • suite_heightnumberrequired“Suite height from average grade (m)”
    • separationnumberrequired“Distance from the main wall of the house (m)”
    • suite_gfanumberrequired“Suite gross floor area, all floors including a basement (m2)”
    • rear_setbacknumberrequired“Rear yard setback (m)”
    • side_setbacknumberrequired“Smallest side yard setback (m)”
    • one_storeystringrequired“Suite is one storey”
    • rear_openingsstringrequired“Rear lot line abuts a residential-zone lot and the rear wall has openings more than 4.0 m above grade”
    • side_openingsstringrequired“Side wall facing a side lot line (not a street) has doors or windows”
  • toronto-permit-review-time-calculator

    “Gives the last day of the City of Toronto published review time for a complete building permit application, by review stream.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 3 required
    • streamstringrequired“Review stream: house = House Stream (10 business days); small = Small Building Stream (15); large = Large and Complex, large building (20); complex = Large and…”
    • datestringrequired“Date the complete application is taken in (YYYY-MM-DD)”
    • zoning_certificatestringrequired“Application includes an issued Zoning Applicable Law Certificate and all fees paid”
  • accessible-ramp-and-doorway-calculator

    “Ramp length for a rise at the Ontario Building Code 1 in 12 gradient, a slope check, or a doorway clear width check, using Section 3.8.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 1 required
    • modestringrequired“len = ramp length needed for a rise (needs rise); slope = check an existing slope (needs rise and run); door = doorway clear width (needs width and door)”
    • unitsstring“Units of rise, run and width”
    • risenumber“Total rise (modes len and slope) (units)”
    • runnumber“Horizontal run (mode slope) (units)”
    • widthnumber“Clear width with the door open (mode door) (units)”
    • doorstring“Which doorway (mode door): path = barrier-free path of travel; suite-wide = bathroom or bedroom door in a suite served by a corridor 1,060 mm or wider; suite-n…”
  • bathroom-exhaust-fan-calculator

    “Minimum bathroom exhaust fan rating in CFM from room size, ceiling height and fixtures, using the Home Ventilating Institute guidance.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    5 inputs, 2 required
    • unitsstring“Units of length, width and height”
    • lengthnumberrequired“Room length (units)”
    • widthnumberrequired“Room width (units)”
    • heightnumber“Ceiling height (units)”
    • fixturesstring“Comma separated fixtures in the room; needed only when the room is over 100 sq ft”
  • basement-ceiling-height-and-egress-checker

    “Tests basement ceiling height, height under beams and ducts, and stair headroom against Ontario Building Code Part 9, for a house basement or a secondary suite.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    9 inputs, 2 required
    • unitsstring“Units of every height”
    • typestringrequired“house = basement of a house without a secondary suite; suite = secondary suite”
    • ceilingnumberrequired“Finished ceiling height over the main part of the space, floor to underside of the finished ceiling (units)”
    • sharenumber“house only: percent of the basement floor area with a ceiling of 2,100 mm or more (default 100 when the ceiling is 2,100 mm or more, otherwise 0) (%)”
    • obstructionnumber“Lowest clear height under a beam or duct (units)”
    • bedroomstring“house only: a bedroom is planned in the basement”
    • bedroom_lownumber“house with bedroom only: lowest ceiling in the bedroom (units)”
    • bedroom_sharenumber“house with bedroom only: percent of the required bedroom floor area with a ceiling of 2,300 mm or more (%)”
    • stairnumber“Clear height over the basement stair, measured from the line through the tread nosings (units)”
  • egress-window-size-calculator

    “Tests a bedroom escape window against Ontario Building Code Article 9.9.10.1: open area of at least 0.35 m2, no dimension under 380 mm, sill height and window well clearance.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 4 required
    • unitsstring“Units of width, height, sill and clearance”
    • typestringrequired“Window type”
    • widthnumberrequired“Clear width of the unobstructed open portion with the window fully open (units)”
    • heightnumberrequired“Clear height of the unobstructed open portion with the window fully open (units)”
    • floorstringrequired“basement = window in a basement area; above = any other floor”
    • sillnumber“Sill height above the floor (tested only when floor is above) (units)”
    • wellstring“The window opens into a window well”
    • well_clearancenumber“Clearance in front of the window inside the well (units)”
  • second-suite-requirements-checklist

    “A checklist of Ontario Building Code, Planning Act, Fire Code and City of Toronto items to check before adding a secondary suite to a house, each with its section number.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    7 inputs, 7 required
    • buildingstringrequired“Existing building type”
    • smallerstringrequired“The new unit will be smaller than the main unit”
    • units_nowstringrequired“Dwelling units in the house now”
    • locationstringrequired“Where the suite will be”
    • fuelstringrequired“A fuel-burning appliance, flue, fireplace or attached garage is in or next to the suite”
    • parkingstringrequired“Parking spaces available for the suite”
    • rentalstringrequired“The suite will be rented”
  • deck-permit-and-guard-checker-toronto

    “Says whether a deck in Toronto needs a building permit, whether a guard is required, the minimum guard height, opening size and stair handrail rule, from the City of Toronto and Ontario Building Code…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs, 4 required
    • unitsstring“Units of height, guard height and gap”
    • heightnumberrequired“Height of the finished deck surface above the adjacent finished grade (units)”
    • attachedstringrequired“The deck is attached to the house”
    • roofedstringrequired“The deck has a roof”
    • exitstringrequired“The deck forms part of an exit required under the Building Code”
    • risersnumber“Number of risers on the deck stairs (whole number)”
    • guard_heightnumber“Planned guard height (units)”
    • gapnumber“Planned clear opening between pickets or balusters (units)”
  • stair-calculator-ontario

    “Gives the number of risers allowed for a total rise, the rise and run of each option, and tests headroom and width against Ontario Building Code Part 9 Section 9.8.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    6 inputs, 1 required
    • unitsstring“Units of rise, run, headroom and width”
    • typestring“private = stairs inside or outside a house or dwelling unit; public = public stairs in a residential building”
    • risenumberrequired“Total rise from finished floor to finished floor (units)”
    • runnumber“Total horizontal run available (units)”
    • headroomnumber“Clear height over the stair (units)”
    • widthnumber“Stair width (units)”
  • renovation-materials-calculator

    “How much paint, how many drywall sheets or how many boxes of flooring a rectangular room needs, with an adjustable waste allowance.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    12 inputs, 3 required
    • materialstringrequired“What to calculate”
    • unitsstring“ft = feet, sq ft and gallons; m = metres, m2 and litres”
    • lengthnumberrequired“Room length (units)”
    • widthnumberrequired“Room width (units)”
    • heightnumber“Ceiling height (paint and drywall) (units)”
    • openingsnumber“Doors and windows to subtract (paint and drywall) (area in sq ft or m2)”
    • ceilingstring“Include the ceiling (paint and drywall)”
    • coatsnumber“Number of coats (paint)”
    • coveragenumber“Coverage printed on the paint can (paint) (sq ft per gallon or m2 per litre)”
    • sheetstring“Drywall sheet length in feet, 4 ft wide (drywall)”
    • box_coveragenumber“Coverage printed on one box of flooring (floor) (sq ft or m2)”
    • wastenumber“Waste allowance in percent (drywall and floor) (%)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-17.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 98
Tools with a description
100% of 11
Typical description length
316 characters

The tool set

Counted from the listing

Tools
11
Size of the list
about 4,604 tokens for an agent to load (characters ÷ 4)
Naming
11 of 11 names use kebab-case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 11 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-17 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://andarehomes.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://andarehomes.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "tools": {
      "type": "http",
      "url": "https://andarehomes.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"tools","type":"http","url":"https://andarehomes.com/mcp"}'
Claude Code
claude mcp add --transport http tools https://andarehomes.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "tools": {
      "type": "streamableHttp",
      "url": "https://andarehomes.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "tools": {
      "httpUrl": "https://andarehomes.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.tools]
url = "https://andarehomes.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "tools": {
      "url": "https://andarehomes.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://andarehomes.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint andarehomes.com/mcpSession openedmatchesour test · 2026-11-17
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-17

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.andarehomes/tools

Answered from the data above

Who publishes com.andarehomes/tools?

The registry ties the namespace com.andarehomes to the domain andarehomes.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.andarehomes/tools need an API key or sign-in?

It opened a session without any credential on 2026-11-17. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.andarehomes/tools been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-17
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-17, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 562 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 11 tools, 0 resources, 0 prompts.
  4. 2,021 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-17
MCP capability
tools
our test · 2026-11-17
Transport
streamable HTTP
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.andarehomes/tools: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/com.andarehomes/tools

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.andarehomes/tools)](https://protocolprobe.com/mcp/servers/com.andarehomes/tools)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology