V2.ai Insights Scraper MCP

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation4/5
Most tools have distinct purposes, but there is some potential overlap between get_latest_posts and get_contentful_posts, as both retrieve posts, though the latter is conditional on Contentful configuration. The other tools (get_post_content, search_blogs, summarize_post) are clearly differentiated by their specific actions on blog content.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case, such as get_contentful_posts, get_latest_posts, get_post_content, search_blogs, and summarize_post. This uniformity makes the tool set predictable and easy to understand.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of scraping and analyzing blog content. Each tool serves a specific function in the workflow, from fetching and searching to summarizing posts, without being overly sparse or bloated.
Completeness4/5
The tool set covers core operations for blog content retrieval and analysis, including fetching, searching, and summarizing. However, there is a minor gap in update or delete operations, which might be outside the scraper's scope, but could limit full lifecycle management if needed.
Average 2.9/5 across 5 of 5 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions fetching posts and a configuration prerequisite, but does not cover critical aspects such as authentication needs, rate limits, error handling, or what the output looks like (e.g., post format, pagination). This leaves significant gaps for an agent to understand how to invoke it safely and effectively.
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?
The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the main action ('Fetch posts'), though the conditional 'if configured' adds minor complexity. Overall, it is appropriately sized for a simple tool but could be more informative.
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?
Given the tool has no annotations, no output schema, and low parameter coverage, the description is incomplete. It does not explain the return values, error conditions, or behavioral details needed for an agent to use it correctly. The conditional 'if configured' is vague, and without sibling differentiation, the context is insufficient for reliable tool selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has one parameter ('limit') with 0% description coverage, and the tool description does not mention any parameters or their semantics. This fails to compensate for the lack of schema documentation, leaving the agent without guidance on what 'limit' controls (e.g., number of posts, pagination) or how it interacts with the fetching behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool 'fetch[es] posts directly from Contentful CMS', which provides a clear verb ('fetch') and resource ('posts from Contentful CMS'). However, it does not differentiate from sibling tools like 'get_latest_posts' or 'search_blogs', leaving ambiguity about its specific scope or filtering capabilities beyond the basic action.
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 includes a conditional clause 'if configured', which hints at a prerequisite but does not explain what configuration is needed or when to use this tool versus alternatives like 'get_latest_posts' or 'search_blogs'. There is no explicit guidance on when to choose this tool over siblings, making usage unclear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns content, implying a read-only operation, but does not cover aspects like error handling (e.g., invalid index), performance, or output format. This is a significant gap for a tool with zero annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste. It is front-loaded with the core purpose and includes necessary details without redundancy, making it appropriately sized and easy to parse.
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?
Given the tool has no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on return values, error cases, and behavioral traits, which are crucial for a read operation. The description does not adequately compensate for the missing structured data.
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 schema description coverage is 0%, so the description must compensate. It adds meaning by specifying that 'index' refers to a blog post index, which is useful beyond the schema's basic type. However, it does not explain index range, format, or examples, leaving some ambiguity, so it partially compensates but not fully.
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 ('Returns') and resource ('full content of the blog post'), specifying what the tool does. However, it does not explicitly differentiate from siblings like 'get_contentful_posts' or 'get_latest_posts', which may also retrieve post content, so it lacks sibling distinction for a perfect score.
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 versus alternatives like 'search_blogs' or 'summarize_post'. It mentions 'at the specified index', which implies usage for a known post index, but does not clarify context, exclusions, or prerequisites, leaving the agent without explicit usage instructions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool searches across multiple fields but does not disclose critical traits like whether it's read-only, how results are ordered, if there's pagination, rate limits, or error handling. For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.
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?
The description is appropriately sized with two concise sentences that directly address the tool's function. It is front-loaded with the core purpose and avoids unnecessary details. However, it could be slightly more structured by explicitly separating scope from field details.
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?
Given the tool's complexity (search functionality with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., list of posts, metadata), how results are formatted, or any limitations. This leaves the agent with insufficient context to use the tool effectively.
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 description adds minimal meaning beyond the input schema. It implies the 'query' parameter searches text across fields like titles and content, but with 0% schema description coverage, the schema provides no details on parameter semantics. The description does not explain the 'limit' parameter or provide syntax examples, so it only partially compensates for the coverage gap.
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's purpose: 'Search blog posts across all content using text query' specifies the verb (search), resource (blog posts), and scope (across all content). It distinguishes from siblings like 'get_contentful_posts' or 'get_latest_posts' by emphasizing search functionality rather than retrieval by specific criteria.
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 versus alternatives. It mentions searching 'titles, content, authors, and other fields' but does not specify when this is preferable over siblings like 'get_latest_posts' for recent content or 'summarize_post' for summaries. No exclusions or prerequisites are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Returns a summary'), which implies it's non-destructive, but doesn't cover aspects like error handling (e.g., what happens if the index is invalid), performance characteristics, or authentication needs. This leaves significant gaps for an agent to understand how to use it effectively.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, direct sentence with zero wasted words. It front-loads the core purpose ('Returns a summary') and efficiently specifies the resource and parameter, making it easy to parse quickly.
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?
Given the complexity of summarizing content, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the summary includes (e.g., length, format), potential limitations, or how it interacts with sibling tools. For a tool that likely involves processing blog posts, more context is needed to guide an agent effectively.
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 has 0% description coverage, so the description must compensate. It adds meaning by specifying that the 'index' parameter refers to a blog post index, which clarifies beyond the schema's generic 'integer' type. However, it doesn't provide details like valid index ranges or how indices are assigned, leaving some ambiguity. Given the single parameter and low schema coverage, this is adequate but not comprehensive.
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's purpose with a specific verb ('Returns a summary') and resource ('blog post at the specified index'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_post_content' or 'search_blogs', which might also retrieve post information, so it falls short of a perfect score.
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 versus alternatives such as 'get_post_content' or 'search_blogs'. It mentions a specific index parameter but doesn't explain prerequisites like needing to know the index beforehand or how it relates to other tools that might list posts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'retrieves' posts, implying a read-only operation, but doesn't specify aspects like rate limits, authentication needs, pagination, or what 'latest' means (e.g., time frame, sorting). This leaves significant gaps for a tool with no structured safety hints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with no wasted words. It front-loads the key action and resource, making it easy to parse quickly, which is ideal for a simple tool with no parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 0 parameters and no output schema, the description is minimally adequate but incomplete. It lacks details on behavioral traits (e.g., how 'latest' is defined, metadata structure) and doesn't differentiate from siblings, which could confuse an agent in a server with multiple post-related tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by specifying 'latest blog posts with metadata', which clarifies the scope and output content beyond what the empty schema provides, earning a baseline score above 3.
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 ('Retrieves') and resource ('latest blog posts with metadata'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_contentful_posts' or 'search_blogs', which likely retrieve similar content but with different scopes or filters.
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 versus alternatives like 'search_blogs' or 'get_contentful_posts'. It implies usage for retrieving latest posts but doesn't specify contexts, exclusions, or prerequisites, leaving the agent to guess based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![v2-ai-mcp MCP server](https://glama.ai/mcp/servers/V2-Digital/v2-ai-mcp/badges/card.svg)](https://glama.ai/mcp/servers/V2-Digital/v2-ai-mcp)

Score Badge

Copy to your README.md:

[![v2-ai-mcp MCP server](https://glama.ai/mcp/servers/V2-Digital/v2-ai-mcp/badges/score.svg)](https://glama.ai/mcp/servers/V2-Digital/v2-ai-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/V2-Digital/v2-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server