nake.si MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_site_overviewA | Fetch only the public homepage https://nake.si/ and return its title, meta description, and up to 20 https links on nake.si. Does not call image or video generation APIs. |
| read_public_pageA | Read one public HTML page on https://nake.si/ only. path must start with /. Any other host is rejected before a request is sent. script tags are removed and the text is capped at 4000 characters. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
get_site_overview and read_public_page overlap somewhat, since read_public_page with path '/' reaches nearly the same content, but the overview tool is distinguished by returning structured metadata (title, description, curated link list). An agent can reasonably tell which to pick: one for a quick site summary, one for fetching a specific page.
Both names are snake_case verb_noun constructions (get_site_overview, read_public_page), which is predictable and readable. Minor inconsistency in verb choice (get vs read) for what are conceptually both retrieval operations.
Two tools is thin for any server, though the stated purpose (read-only access to a single public site) is narrow enough that a large surface isn't warranted. The overview tool is arguably a convenience wrapper over the page reader, so the set feels borderline rather than complete.
Covers the basics of reading a public site, but has notable gaps: no way to discover pages beyond the 20 links on the homepage, no search or sitemap/listing operation, and no link-following or crawl capability. Agents hitting a page whose links are truncated will have no workaround.