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.

ScareMap

REMOTE · WWW.SCAREMAP.APP

Find haunted houses, ghost tours and haunted places near you, with visitor ratings.

Available components

+3 this week 80 Trust /100

Last scanned (22 minutes ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

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 Security80
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 922 tokens (~230/item across 4 items; 4 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 Management57
  • Stability observed for 17 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
  • 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 29 Oct 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.

  • 27 Oct 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.

  • 25 Oct 26 +1

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

  • 23 Oct 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.

  • 21 Oct 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.

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 5 Nov 2026 · Probed https://www.scaremap.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.scaremap.app CN=YR1,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 RSA 2048 SHA256-RSA 615bd74177bdc8670c4a0155b24b4c271b5
SANs: www.scaremap.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 www.scaremap.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
scaremap.app. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.scaremap.app/mcp Verified 200
http (plaintext) http://www.scaremap.app/mcp HTTPS enforced 308 https://www.scaremap.app/mcp
MCP tools · 4 exposed · ~729 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
scaremap_categories ~61

List every haunt category with its display label and the number of public haunts in it. Call this first when the user asks what kinds of places ScareMap covers, or to get valid values for the category filter on the other tools. Takes no input.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–
total_hauntsnumberyes–

No examples provided.

scaremap_find_haunts ~293

Find haunted houses, haunt farms, ghost tours, horror escape rooms and haunted places within a radius of a latitude/longitude, nearest first. Call this when the user gives a place, address or coordinates and wants scary things to do nearby. Geocode a place name to lat/lng first; this tool does not search by name. Filter by category, by season, or by minimum visitor ratings. Unrated haunts (review_count 0) have null ratings and are left out when min_stars or min_scare is set. For a whole city or state use scaremap_find_haunts_in_city. For the full record and reviews of one result use scaremap_get_haunt.

NameTypeReqDescription
categorystring–Only this category. Call scaremap_categories for the list.
latnumberyesLatitude of the search center, decimal degrees.
limitinteger–Maximum results. Default 10, maximum 25.
lngnumberyesLongitude of the search center, decimal degrees.
min_scarenumber–Minimum average scare intensity (1 to 5).
min_starsnumber–Minimum average quality rating (1 to 5).
radius_milesnumber–Search radius in miles. Default 25, maximum 150.
seasonstring–halloween = seasonal haunt, year_round = open outside October.
NameTypeReqDescription
hauntsarrayyes–
total_matchesnumberyesMatches inside the radius before the limit is applied.

No examples provided.

scaremap_find_haunts_in_city ~230

List haunts in a US state, or in one city of that state, using the same state and city grouping as the ScareMap location pages. Call this when the user names a state or city ("haunted houses in Salem, Massachusetts") and has no coordinates. State accepts a name, a slug or a two-letter code. Results are ordered by review count, then name. If the city is not found, the error lists the cities ScareMap has in that state. To search by distance from a point use scaremap_find_haunts.

NameTypeReqDescription
categorystring–Only this category. Call scaremap_categories for the list.
citystring–City name within the state. Omit to list the whole state.
limitinteger–Maximum results. Default 25, maximum 50.
seasonstring–halloween = seasonal haunt, year_round = open outside October.
statestringyesState name, slug or two-letter code, for example "Massachusetts", "new-york" or "TX".
NameTypeReqDescription
citystring|nullyes–
hauntsarrayyes–
page_urlstringyesScareMap location page for this state or city.
statestringyes–
total_matchesnumberyes–

No examples provided.

scaremap_get_haunt ~145

Get the full record for one haunt: description, category, season, location, average ratings, and up to 20 of the newest visitor reviews (stars, scare, text, date). Call this after scaremap_find_haunts or scaremap_find_haunts_in_city when the user wants detail on a specific result. Pass the slug from those results, or the haunt id. Reviews are anonymous. A haunt with no reviews returns an empty list.

NameTypeReqDescription
idstring–Haunt UUID. Use instead of slug.
slugstring–Haunt slug from other ScareMap tools, for example "hellscream-haunted-house".
NameTypeReqDescription
hauntobjectyes–
reviewsarrayyes–

No examples provided.

Install

How do I install the ScareMap MCP server?

ScareMap is a hosted endpoint at https://www.scaremap.app/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 · www.scaremap.app

# add to Claude Code
claude mcp add --transport http app-scaremap-scaremap 'https://www.scaremap.app/mcp'
Common questions

What is the ScareMap MCP server?

ScareMap is an MCP server listed in the public MCP registry as app.scaremap/scaremap. Find haunted houses, ghost tours and haunted places near you, with visitor ratings. This page covers its hosted endpoint (https://www.scaremap.app/mcp).

Is the ScareMap MCP server safe to use?

ScareMap scores 80 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 ScareMap MCP server expose?

ScareMap exposes 4 tools: scaremap_find_haunts, scaremap_find_haunts_in_city, scaremap_get_haunt, scaremap_categories. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

Does the ScareMap MCP server require authentication?

No. We connected to ScareMap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ScareMap MCP server still maintained?

ScareMap is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.