Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Intertwine House Plans: Plan Finder

REMOTE · AGENTS.INTERTWINEHOUSEPLANS.COM

Search Angela Kamer's coastal house plans by beds, sq ft, lot width, pilings and elevator.

+3 this week 71 Trust /100

Last scanned (14 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1823 tokens (~303/item across 6 items; 6 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 Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Server version: 1.2.1 → 1.2.2 functional
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 65

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://agents.intertwinehouseplans.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=intertwinehouseplans.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 27686c3cfaf00e6513f113aa6747a37c
SANs: intertwinehouseplans.com, agents.intertwinehouseplans.com, *.agents.intertwinehouseplans.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agents.intertwinehouseplans.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
intertwinehouseplans.com. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.intertwinehouseplans.com/mcp Verified 200
http (plaintext) http://agents.intertwinehouseplans.com/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,738 tokens

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 →

Tool Tokens
about_designer ~124

Get background on the designer and how buying from her works. Takes no arguments. Returns a fixed summary: designer (Angela Kamer, residential designer), background (training and coastal experience), what the store sells, plan set formats, how $75 study sets work and are credited, how modifications are quoted, the modification request link, the number of plans and the list of buying_help topics. Use this when the buyer asks who drew the plans or how ordering works in general; use buying_help for a specific pre-purchase question and get_plan for a specific plan. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

buying_help ~219

Answer a buyer's question before purchase using the store's own help pages. Pick one topic: whats_included (what a plan set contains and doesn't), study_sets (the $75 preview set and its credit), modifications (how changes are quoted and requested), cost_to_build (why there is no calculator and how to get a real number), built_homes (plans that have been built, with photos) or faq (the store's live FAQ). For faq, pass `question` to return only entries whose question or answer contains one of its words. Returns { topic, title, page } with the answer text; faq adds questions[] (question and answer pairs) and built_homes adds plans[] in search_plans form. Use get_plan for questions about one plan's specs or price. Read-only.

NameTypeReqDescription
questionstring–Only used with topic faq: words to match against FAQ questions, for example license, permit or engineer.
topicstringyesWhich help topic to return; see the description for what each covers.

No output schema declared.

No examples provided.

get_plan ~273

Get the complete record for one house plan. Use this after search_plans or plans_for_lot, or when the buyer names a plan. Accepts the plan's name, any other name it is published under, or its URL handle (for example The Heron, Lambert's Cottage or the-heron); matching is case-insensitive, ignores a leading "The" and falls back to a partial name match. Returns specs (bedrooms, baths, heated and total sq ft, stories, width, depth, max ridge height, ceilings, roof pitch, framing, garage, ground level), yes/no flags for elevated, elevator, drive-under, in-law suite and garage ADU, the narrowest lot it suits, foundation options with any added fee, every package (PDF, PDF plus CAD, Chief Architect) with current and regular price, image URLs, the full design write-up, the $75 study set link, the change request link, a built-home link when one exists, other published names and the plan page URL. If no plan matches, it returns an error that says to use search_plans. Read-only.

NameTypeReqDescription
planstringyesPlan name, other published name, or URL handle, for example "The Heron", "Lambert's Cottage" or "the-heron".

No output schema declared.

No examples provided.

list_features ~119

List every style and feature value the catalog uses, with how many plans carry each. Takes no arguments. Returns { totalPlans, features } where features maps each value (for example "elevated coastal": 39, "elevator": 21) to its count across all 68 plan sets; a plan can carry several. Use this to see what the catalog offers before searching, or to pick a valid `feature` value for search_plans. It returns counts only; use search_plans to get the plans themselves. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plans_for_lot ~320

Find the plans whose house footprint fits a specific lot. Use this when the buyer gives lot width and depth; use search_plans when they only describe the house. Subtracts the setbacks from the lot (side setback from each side, plus front and rear), then returns { buildableArea, matches, plans[], note }: the buildable rectangle, the number of plans that fit, up to `limit` of them largest first with the same fields as search_plans, and a reminder that porches and stairs can extend past the footprint. This is a first screen only. Setbacks, flood zone, height limits and local codes must be confirmed with the jurisdiction and the designer. Read-only.

NameTypeReqDescription
elevatedboolean–true to return only raised-foundation plans (pilings, piers or elevated CMU).
frontSetbackFtnumber–Required front setback, in feet. Defaults to 20.
limitinteger–How many fitting plans to return (1 to 25), largest heated area first.
lotDepthFtnumberyesLot depth from street to rear line, in feet.
lotWidthFtnumberyesLot width along the street, in feet.
minBedroomsnumber–Fewest bedrooms, counting optional bedrooms.
rearSetbackFtnumber–Required rear setback, in feet. Defaults to 15.
sideSetbackFtnumber–Required setback on each side, in feet. Defaults to 5 if the buyer doesn't know.

No output schema declared.

No examples provided.

search_plans ~683

Find house plans in the Intertwine House Plans catalog (68 plan sets by residential designer Angela Kamer) that match a buyer's requirements. Use this first when someone describes the house they want: bedrooms, baths, size, width, an elevated or pilings foundation, an elevator, a drive-under garage, an in-law suite, a garage apartment, a style or a budget. All filters are optional and combine with AND; leave out any the buyer didn't mention. Returns { count, plans[] } where count is the total number of matches and plans holds up to `limit` of them in catalog order, each with name, subtitle, bedrooms (and optional bedrooms), baths, heated sq ft, stories, footprint, foundation, features, starting price (plus the regular price when a sale is on), one photo URL and the plan's page URL. Use get_plan for everything about one plan, plans_for_lot when the buyer gives lot dimensions, and list_features to see which style and feature values exist. Read-only; it never buys or changes anything.

NameTypeReqDescription
driveUnderboolean–true for plans with a drive-under garage beneath the living floors.
elevatedboolean–true for plans built on a raised foundation (pilings, piers or an elevated base) for flood zones and coastal lots; false for plans that are not raised.
elevatorboolean–true for plans with an elevator.
featurestring–One style or feature to filter by, case-insensitive. Use pilings and stilts or elevated coastal for raised coastal homes. list_features shows how many plans carry each value.
garageADUboolean–true for detached garage plans that include an apartment or ADU above or beside the garage.
inLawSuiteboolean–true for plans with a bedroom and full bath set apart for a guest or relative.
limitinteger–How many plans to return (1 to 25). count still reports every match.
maxBedroomsnumber–Most bedrooms, counting only standard bedrooms.
maxDepthFtnumber–Deepest the house footprint can be, in feet.
maxPricenumber–Highest starting price in US dollars, using the current price (sale price when a sale is on).
maxSqFtnumber–Largest heated (living) area in square feet.
maxWidthFtnumber–Widest the house footprint can be, in feet. For a full lot check with setbacks, use plans_for_lot instead.
minBathroomsnumber–Fewest bathrooms; half baths count as 0.5 (for example 2.5).
minBedroomsnumber–Fewest bedrooms. Counts optional bedrooms, so a 3-bedroom plan with an optional 4th matches minBedrooms 4.
minSqFtnumber–Smallest heated (living) area in square feet. Garages, porches and ground-level storage aren't included.
storiesinteger–Exact number of stories as the plan lists them (the catalog has 1- and 2-story plans).
textstring–Words to find in a plan's name, other published names, subtitle or summary, for example porch, courtyard or Lambert's Cottage. Case-insensitive substring match.

No output schema declared.

No examples provided.

Install

How do I install the Intertwine House Plans: Plan Finder MCP server?

Intertwine House Plans: Plan Finder is a hosted endpoint at https://agents.intertwinehouseplans.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 · agents.intertwinehouseplans.com

# add to Claude Code
claude mcp add --transport http atlasdigitaldesign-intertwine-plans 'https://agents.intertwinehouseplans.com/mcp'
Common questions

What is the Intertwine House Plans: Plan Finder MCP server?

Intertwine House Plans: Plan Finder is an MCP server listed in the public MCP registry as io.github.AtlasDigitalDesign/intertwine-plans. Search Angela Kamer's coastal house plans by beds, sq ft, lot width, pilings and elevator. This page covers its hosted endpoint (https://agents.intertwinehouseplans.com/mcp).

Is the Intertwine House Plans: Plan Finder MCP server safe to use?

Intertwine House Plans: Plan Finder scores 71 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 Intertwine House Plans: Plan Finder MCP server expose?

Intertwine House Plans: Plan Finder exposes 6 tools: search_plans, get_plan, plans_for_lot, list_features, about_designer, buying_help. Their descriptions and schemas cost roughly 1,738 tokens of context every time the server is loaded.

Does the Intertwine House Plans: Plan Finder MCP server require authentication?

No. We connected to Intertwine House Plans: Plan Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Intertwine House Plans: Plan Finder MCP server still maintained?

Intertwine House Plans: Plan Finder is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Intertwine House Plans: Plan Finder MCP server?

VerifyMCP ran 12 checks on Intertwine House Plans: Plan Finder, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Intertwine House Plans: Plan Finder: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.