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.
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.
Tool Definition Quality
Average 4.7/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
With a single tool, naming consistency is not a concern. The name 'phoenix_relink_check' follows a clear verb_noun pattern and is descriptive.
The server has a single tool, which is slightly thin but appropriate for its very specific compliance screening purpose. The tool description fully covers the intended use case.
The single tool appears to cover the core functionality implied by the server name. No obvious gaps are present, as the tool's description includes its use in multiple diligence scenarios.
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.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully discloses behavior: fuzzy matching, use of two independent signals, filtering of shared commercial registered-agent addresses, and output of non-conclusory review flags with evidence chain and links. No hidden aspects remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured paragraph that front-loads the core purpose and logically proceeds to details. Every sentence contributes meaning without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (single parameter, no output schema), the description provides complete context: input expectations, processing logic, output characteristics, and usage scenarios. No gaps are evident.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'name' is described in the schema but the description adds value by providing examples (debarred contractor, excluded provider, OFAC-listed party) and clarifying the role as a principal or entity name, which aids in correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: detecting phoenix/rebrand relinks that exact-match screeners miss. It specifies the input (principal or entity name) and the detailed logic, making it highly distinct.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly mentions use during M&A diligence, vendor/counterparty onboarding, or compliance screening. It also clarifies what the tool does not do (returns research leads, not determinations). However, it does not discuss when not to use or provide alternatives.
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!