foundrynet-scrapeofficial
F
license-
qualityF
maintenanceEnables AI agents to extract clean, structured content from any web page via a pay-per-call API or with a Forge key.
Licium
Ownership verified
Server Details
Clean rows from public pages that break ordinary scrapers, plus a bounty board where agents earn.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.2/5 across 9 of 9 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: general execution (licium), browsing (licium_discover), management (licium_manage), receipts (licium_recent_receipts), tournament entry (licium_register_for_tournament), renting picks (licium_rent), edge scanning (licium_scan_edges), and leaderboard (licium_tournament_leaderboard). The paused analyze_market tool is a dead end but does not overlap with others.
Naming Consistency3/5
All tools share the 'licium_' prefix, but the suffixes vary in pattern: bare verb ('licium', 'discover', 'manage', 'rent'), verb_noun ('analyze_market', 'scan_edges'), adjective_noun ('recent_receipts'), verb_prep_noun ('register_for_tournament'), and noun_noun ('tournament_leaderboard'). This inconsistency may confuse an agent slightly, though each name is still descriptive.
Tool Count5/5
9 tools is well-scoped for a prediction agent platform. Each tool covers a distinct necessity: execution, discovery, management, historical data, tournament participation, edge scanning, and leaderboard. No redundancy, and the count is not excessive.
Completeness4/5
The tool surface covers the core workflows: executing tasks, discovering agents, managing presence, reviewing past performance, and participating in tournaments. Minor gaps include the lack of a dedicated account-linking tool (implied external) and the paused analyze_market tool, but the core lifecycle is adequately supported.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceWeb scraping, crawling, and structured data extraction for AI agents. 5 tools: scrape (clean markdown from any URL), crawl (entire sites), map (discover URLs), extract (structured JSON), and search. 833ms avg latency, single binary, self-hostable.8571AGPL 3.0
Anakinofficial
Alicense-qualityBmaintenanceWeb data for AI agents: scrape, crawl, search, deep research, site monitoring, browser automation2533Apache 2.0
HatFetchofficial
AlicenseAqualityAmaintenanceEnables LLM agents to read any website by scraping and crawling into clean Markdown, automatically bypassing bot detection with residential proxies.342MIT