Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / topo^alpin
topo^alpin
by topoalpin.app · https://api.topoalpin.app/mcp
Avalanche danger level at any place in the Alps, from official warning services.
11 of 11 checks · 6 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 4 tools
- Its own safety labels
- 4 read-only
- Memory it takes
- About 1,500 tokens of your AI's memory, just for its tool descriptions
- Largest answer
- About 15.8 KB in our test
- Speed
- Average answer in our test: 132 ms
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 6 Nov 2026.
Is topo^alpin MCP server safe?
- None of the hidden-instruction wordings we know were found in its 4 tool descriptions.
- Its error messages showed no secrets or internal details.
- All 4 of its tools are labeled read-only.
- Overall it scored 93/100 on 6 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
4 tools, in the server's own words.
avalanche_coverageread-onlyIs there an avalanche report at all right now, and in which regions?
avalanche_regionread-onlyDoes a summit, destination or point lie in an avalanche warning region of the Alps, in which one, and does it have a current report?
avalanche_overviewread-onlyHow is the avalanche situation in a wider area of the Alps, such as Tyrol or the Valais?
avalanche_bulletinread-onlyThe danger level where someone is going in the Alps, from the official avalanche bulletin: give a place name or the name of a warning region, or lat and lon, o…
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Every tool is describednote
1 warning
- !avalanche_region: Inputs with no description: points
- ✓ConnectsConnected in 526 mspass
- ✓Ready for the newest MCP versionUses the latest MCP version (2026-07-28)pass
- ✓Lists its toolsFound 4 toolspass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Tools work with good inputspass
All good
- ✓avalanche_coverage: Worked (206 ms)
- ✓avalanche_region: Answered with an error, probably because of our sample input: Happy to check: please give the name of a place (query) or a list of points.
- ✓avalanche_overview: Answered with an error, probably because of our sample input: Happy to check: please give one of these, the name of a place or region (query), lat and lon together, or a warning service.
- ✓avalanche_bulletin: Answered with an error, probably because of our sample input: Happy to check: please give one of these, the name of a place or region (query), lat and lon together, or a region id.
- ✓Bad inputs give a clean errorpass
All good
- ✓avalanche_coverage: Refused wrong type for "service" with a clear error
- ✓avalanche_region: Refused wrong type for "query" with a clear error
- ✓avalanche_overview: Refused wrong type for "query" with a clear error
- ✓avalanche_bulletin: Refused wrong type for "query" with a clear error
- ✓Fast enoughpass
All good
- ✓Connecting took 526 ms
- ✓Listing tools took 436 ms
- ✓Average tool answer: 132 ms
- ✓avalanche_coverage: Slowest tool: avalanche_coverage (206 ms)
- ✓No secrets leakedChecked 9 error messages: no secrets or internal detailspass
- ✓Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guidepass
- –Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://api.topoalpin.app/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/app-topoalpin-mcp.html)Score over time
- 6 Nov 202693
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use topo^alpin, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works