A
licenseNot graded
qualityC
maintenanceEnables AI agents to safely query Kingdee Cloud Galaxy ERP with read-only mode, write confirmation gates, and full audit logging.
AGPL 3.0
AP Control Labs Finance Controls
Server Details
Read-only finance and operations controls for AI agents with evidence and safe next actions.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
check_tax_form1 field changed- added
Input schema / properties / signature_required_by_customerAdded value: +{ + "default": true, + "type": "boolean" +}
32 tool updates
- First observed
analyze_invoice - First observed
check_certificate_expiry - First observed
check_procurement_agent_action - First observed
check_remittance_change - First observed
check_tax_form - First observed
check_vendor_domain_risk - First observed
check_vendor_onboarding - First observed
compare_quotes - First observed
create_purchase_order - First observed
diff_purchase_order_amendment - First observed
extract_contract_obligations - First observed
extract_purchase_order - First observed
get_invoice_exceptions - First observed
get_invoice_extraction - First observed
get_invoice_risk_score - First observed
get_invoice_status - First observed
get_purchase_order_extraction - First observed
match_invoice - First observed
match_reconciliation - First observed
match_remittance_advice - First observed
normalize_bank_statement - First observed
normalize_invoice_lines - First observed
preflight_erp_bill - First observed
preflight_franchise_invoice - First observed
preflight_freight_invoice - First observed
preflight_subcontractor_invoice - First observed
record_receipt - First observed
resolve_vendor_entity - First observed
save_extracted_purchase_order - First observed
search_invoice_history - First observed
upsert_vendor_baseline - First observed
validate_invoice
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Read-only checks for proposed orders against evidence and policy; no trading or payment authority.
21Read-only AI search visibility data: citations, AEO audits, and advisor insights from AI-Advisors.
Read-only Increase banking observability plus one safe non-money-moving write, for AI agents.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and audit Azure Landing Zones by inventorying resources, auditing tagging, evaluating policy compliance, and detecting infrastructure drift, all in read-only mode.-
- AlicenseNot gradedqualityCmaintenanceEnables warehouse operations agents to inspect tasks, deliveries, stock, and KPIs, and to attempt write operations in shadow mode with human approval and segregation of duties enforced as code.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation4/5
Most tools have clearly distinct purposes, but the high number of 'check', 'preflight', and 'match' tools could cause some confusion. For example, analyze_invoice and search_invoice_history both relate to duplicate detection, though one is async and one is direct. Overall, descriptions help differentiate.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_invoice, check_remittance_change, preflight_freight_invoice). There are no mixed conventions or camelCase, making the naming highly predictable.
Tool Count2/5
With 32 tools, this far exceeds the 25-tool threshold for a heavy toolset. While the broad AP controls domain justifies some breadth, the large number, including many private preview tools, makes the surface feel bloated and may overwhelm agents.
Completeness4/5
The tool set covers a wide range of AP control workflows: invoice validation, matching, duplicate detection, PO management, vendor checks, remittance, reconciliation, and preflight checks. Minor gaps exist, such as no direct PO update tool, but core processes are well supported.