Skip to main content
Glama
jkingsman

https://github.com/jkingsman/qanon-mcp-server

by jkingsman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_post_by_id_toolB
Retrieve a specific post by its ID.

Args:
    post_id: The ID of the post to retrieve
search_postsB
Search for posts/drops containing a specific keyword or phrase.

Args:
    query: The keyword or phrase to search for
    limit: Maximum number of results to return (default: 10)
get_posts_by_dateB
Get posts/drops within a specific date range.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format (defaults to start_date if not provided)
    limit: Maximum number of results to return (default: 10)
get_posts_by_author_idB
Get posts/drops by a specific author ID.

Args:
    author_id: The author ID to search for
    limit: Maximum number of results to return (default: 10)
analyze_postB
Get detailed analysis of a specific post/drop including references and context.

Args:
    post_id: The ID of the post to analyze
get_timeline_summaryB
Get a timeline summary of posts/drops, optionally within a date range.

Args:
    start_date: Optional start date in YYYY-MM-DD format
    end_date: Optional end date in YYYY-MM-DD format
word_cloud_by_post_idsA
Generate a word cloud analysis showing the most common words used in posts within a specified ID range.

Args:
    start_id: Starting post ID
    end_id: Ending post ID
    min_word_length: Minimum length of words to include (default: 3)
    max_words: Maximum number of words to return (default: 100)
word_cloud_by_date_rangeB
Generate a word cloud analysis showing the most common words used in posts within a specified date range.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format
    min_word_length: Minimum length of words to include (default: 3)
    max_words: Maximum number of words to return (default: 100)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
qanon://posts/count
qanon://authors
qanon://stats
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes: retrieval by ID, author, date, search, timeline summary, and word cloud generation. However, 'analyze_post' and 'get_post_by_id_tool' could cause confusion as both target specific posts, with 'analyze_post' implying deeper analysis but overlapping in core retrieval functionality. The word cloud tools are clearly differentiated by date vs. ID range.

Naming Consistency3/5

The naming is mixed: some tools use verb_noun patterns like 'search_posts' and 'analyze_post', while others use noun_verb patterns like 'get_post_by_id_tool' and 'get_posts_by_author_id'. There's inconsistency in verb usage ('get', 'analyze', 'search') and structure, but names remain readable and descriptive overall.

Tool Count5/5

With 8 tools, this server is well-scoped for analyzing and retrieving posts/drops in a QAnon context. The count is reasonable, covering key operations like retrieval, search, timeline summary, and word cloud analysis without being overwhelming or too sparse.

Completeness4/5

The tool surface is largely complete for a read-only analysis server, covering retrieval by various criteria, search, timeline summaries, and word cloud generation. A minor gap is the lack of update or delete operations, but given the domain (likely analyzing historical data), this is acceptable, and agents can work around it effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources