B

api.flaim.app

https://api.flaim.app/mcp
84/100 · MCP Trust Grade · checked 4h ago · MCP 2025-06-18
✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 9 tools · Maps & Geo

get_user_session

Use only for fantasy sports questions that need the user's connected league data; do not call for generic coding, scraping, weather, travel, betting,

get_ancient_history

Use this only after get_user_session, and only when the user is clearly asking about a non-current season or an inactive league. This is the historica

get_league_info

Strongly encouraged as the second call after get_user_session for the specified league. This provides the baseline league context for analysis: league

get_standings

Get season standings and outcome snapshot; includes verified season-outcome fields when available. Returns team records, rankings, and points summarie

get_matchups

Get matchups/scoreboard for a specific week or the current week. Best used after get_user_session and after get_league_info for the specified league s

get_roster

Get roster details for a specific team. Exact payload varies by platform: ESPN and Yahoo return player entries with lineup/position context, while Sle

get_free_agents

Get currently available players for the specified league, optionally filtered by position. Exact payload varies by platform: ESPN and Yahoo include ow

get_players

Search for player identity by name. Always returns identity fields, but ownership context varies by platform. ESPN and Yahoo return market/global owne

get_transactions

Get recent league transactions including adds, drops, waivers, and trades. Best used after get_user_session and usually after get_league_info so the m

Spec conformance20%80
Security (OWASP MCP)30%100
Reliability / performance20%70
Tool hygiene15%73
Transparency / provenance15%90

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.
Grade another server

We re-grade api.flaim.app on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — api.flaim.app grade B
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade B · wmcp.sh
[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/api.flaim.app/badge.svg)](https://wmcp.sh/mcp/grade/api.flaim.app)
<a href="https://wmcp.sh/mcp/grade/api.flaim.app"><img src="https://wmcp.sh/mcp/grade/api.flaim.app/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.