A
license-
qualityA
maintenanceResolves messy financial institution records against canonical regulatory identifiers from FDIC, NCUA, and FFIEC public datasets.
MIT
phoenix-screen
Server Details
Phoenix/rebrand relink detection: links a debarred principal to a newly-formed business entity.
- Status
- Healthy
- 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.5/5.0
Tool DescriptionsA
Average 4.6/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined and distinct.
Naming Consistency5/5
Since there is only one tool, naming consistency is not applicable; the single name follows a descriptive pattern.
Tool Count3/5
One tool is minimal but acceptable for a highly specialized compliance-check server. However, it feels thin for a general screening server.
Completeness4/5
The tool provides a thorough evidence chain for phoenix/rebrand detection, covering the core function. Missing complementary tools like entity lookup or watchlist search are minor gaps.
Available Tools
1 toolphoenix_relink_checkAInspect
Detect a phoenix / rebrand relink that exact-match screeners miss. Given a principal or entity name (e.g. a debarred contractor, an excluded provider, or an OFAC-listed party), this fuzzy-relinks it to NEWLY-FORMED Secretary-of-State business entities that share the name AND a second independent signal (principal address or named registered agent), while filtering out shared commercial registered-agent addresses. Returns NON-CONCLUSORY review flags with the full evidence chain and primary-source links — a research lead for human diligence, never a determination of wrongdoing. Use during M&A diligence, vendor/counterparty onboarding, or compliance screening.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Principal or entity name to check for phoenix relinks (e.g. a debarred/excluded/sanctioned party). |
Tool Definition Quality
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully discloses behavioral traits: it returns non-conclusory review flags with full evidence chain and primary-source links, filters out shared commercial registered-agent addresses, and positions the output as a research lead for human diligence. No contradictions.
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 somewhat lengthy but each sentence adds value, and the main purpose is front-loaded. It could be slightly more concise without losing key information, but overall it is well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description thoroughly explains return values (non-conclusory review flags, evidence chain, links) and the matching logic. For a single-parameter tool, it provides complete context for effective use.
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 already covers the single parameter 'name' with a description. The tool description adds contextual examples (e.g., 'a debarred/excluded/sanctioned party') but does not provide substantial new meaning beyond the schema. Baseline 3 is appropriate due to high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool detects phoenix/rebrand relinks that exact-match screeners miss, specifies the input (principal or entity name), and describes the fuzzy matching logic. It distinguishes itself from exact-match screeners, making the purpose specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool ('Use during M&A diligence, vendor/counterparty onboarding, or compliance screening') and clarifies what it does not do (returns non-conclusory review flags, never a determination). This provides clear usage context and exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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
- AlicenseAqualityAmaintenanceEnables named-entity attribution from Certificate Transparency logs (OV/EV only) for mapping legal-entity digital footprints and domain discovery via LLM-driven workflows.2161MIT
- AlicenseAqualityCmaintenanceCompanyLens MCP gives your AI assistant access to real corporate data from official government sources. No web scraping, no hallucinations — verified data from SEC EDGAR, UK Companies House, OpenSanctions, and USAspending.gov.52014MIT
- AlicenseAqualityBmaintenanceResolves messy company, customer, and vendor names across CRM, ERP, and ITSM systems to canonical records using fuzzy matching, preventing AI agents from updating or creating wrong or duplicate records.5MIT