F
licenseNot graded
qualityD
maintenanceAn mcp server for vikingdb store and search.
5
-
mmnt-mcp-server
by zbkm
The mmnt-mcp-server allows you to interact with the Mamont search engine through two main functions:
Search: Use the
mmnt_searchtool to query the Mamont search engine by providing a query string and page number.Cache Retrieval: Use the
mmnt_cachetool to fetch cached search results by providing a unique cache ID, with an option to retrieve text-only content or include HTML.
Provides integration with the Mamont search engine, allowing for executing search queries and retrieving cached web pages from the Mamont search index.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mmnt-mcp-serversearch for recent AI developments"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mmnt-mcp-server
MCP server for the Mamont search engine.
Tools:
mmnt_search
search query on search engine
inputs
query - query string
page - page number
mmnt_cache
retrieve page from search page cache
inputs
id - unique cache id
onlyText - should the result be text only (no html)
Install
{
"mcpServers": {
"mmnt": {
"command": "npx",
"args": ["-y", "mmnt-mcp-server"]
}
}
}Available Tools
2 toolsmmnt_cacheC
Extract page from Mamont cache
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | unique cache id | |
| onlyText | Yes | Should the result be text only (no html) |
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description is too brief to convey behavioral traits such as error handling, idempotency, or side effects. The agent gains little insight beyond the name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, no fluff. Could be slightly expanded with key details without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite simple parameters, the tool lacks context on return value, error conditions, or how 'onlyText' affects output. Incomplete for an agent to use reliably.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already fully describes the two parameters with descriptions. The tool description adds no extra meaning beyond the schema, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'extract page' and the resource 'Mamont cache'. However, it does not differentiate from the sibling tool 'mmnt_search', which likely serves a different purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus the alternative 'mmnt_search'. No context on prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
mmnt_searchC
Search in Mamont search engine
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | query string | |
| page | Yes | page number |
TDQS
C2.4/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description alone must disclose behavioral traits. It only says 'Search in Mamont search engine' without indicating whether the operation is read-only, any side effects, authentication needs, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is concise but lacks depth. It could include more context without being verbose, so it is adequate but not exemplary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema and annotations, the description should provide complete guidance on the tool's behavior and return values. It fails to explain what the search returns, pagination details, or any constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100% with descriptions for both parameters. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs a search in the Mamont search engine, which is a specific verb-resource combination. Although it does not explicitly differentiate from the sibling mmnt_cache, the distinct resource and action imply differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool vs. alternatives, such as mmnt_cache. There is no mention of context, prerequisites, or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- First observed
mmnt_cache - First observed
mmnt_search
TDQS
B3.1/5.0
Scored across 2 tools
Disambiguation5/5
The two tools serve clearly distinct purposes: one extracts cached pages and the other performs searches. There is no overlap or ambiguity between them.
Naming Consistency4/5
Both tools share the consistent 'mmnt_' prefix and lowercase style, though one uses a noun (cache) and the other a verb (search). Minor deviation but overall coherent.
Tool Count4/5
With only two tools, the server is minimal, but this is appropriate for the narrow scope of interfacing with Mamont's search and cache features. It feels slightly thin but not inadequate.
Completeness4/5
The core functionalities of Mamont—searching and retrieving cached pages—are covered. Additional features like pagination or metadata retrieval are minor gaps that an agent can work around.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
MCP server for Russian books search, details, and recommendation candidates.
MCP server for Speech-to-Text
Related MCP Servers
Polygon-io MCP Serverofficial
AlicenseCqualityCmaintenanceAn MCP server for Massive.com Financial Market Data253391MIT- -licenseNot gradedqualityNot gradedmaintenanceMCP Server for ZeroEntropy collections, top documents and rerankers-
- AlicenseNot gradedqualityDmaintenanceMCP server for the Meshimize agent communication platform: Q\&A groups, messaging and group discovery32 npm1MIT