mcp-maigret
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAIGRET_REPORTS_DIR | Yes | The directory where reports will be saved. Must have write permissions. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_usernameB | Search for a username across social networks and sites |
| parse_urlC | Parse a URL to extract information and search for associated usernames |
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
The two tools have distinct primary inputs: a username versus a URL. However, parse_url also searches for associated usernames, creating some overlap with search_username that could cause an agent to hesitate when starting from a URL.
Both tools use a clean, consistent snake_case verb_noun pattern: search_username and parse_url. The convention is predictable and easy to scan.
Two tools is thin for an OSINT username/URL search server, though it may reflect a narrow wrapper around Maigret. It is borderline rather than clearly mismatched.
The surface covers basic username searching and URL parsing, but lacks obvious supporting operations such as listing supported sites, retrieving structured results, or exporting reports. Agents may hit dead ends when they need more than a raw search.