F
licenseNot graded
qualityC
maintenanceEnables authenticated MCP apps to expose and interact with Auth0 Forms, submitting form data directly to Auth0 while only completion status is returned to the agent.
MoneyMCP
Server Details
Securely creates and transfers users to MyWage through the documented partner workflow.
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
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 tooltransfer_userTransfer user to MyWageBInspect
Creates a MyWage user with the supplied personal, employment and financial data. Only email is required.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| iban | No | ||
| Yes | |||
| gender | No | ||
| street | No | ||
| channel | No | ||
| birthday | No | ||
| job_type | No | ||
| postcode | No | ||
| last_name | No | ||
| tax_class | No | ||
| first_name | No | ||
| net_income | No | ||
| partner_id | No | ||
| total_debt | No | ||
| nationality | No | ||
| house_number | No | ||
| loan_purpose | No | ||
| monthly_rent | No | ||
| phone_number | No | ||
| schufa_entry | No | ||
| employer_city | No | ||
| employer_name | No | ||
| family_status | No | ||
| academic_title | No | ||
| place_of_birth | No | ||
| employer_street | No | ||
| living_situation | No | ||
| employer_postcode | No | ||
| is_property_owner | No | ||
| registration_mode | No | ||
| small_loan_amount | No | ||
| number_of_children | No | ||
| pension_start_date | No | ||
| adults_in_household | No | ||
| small_loan_duration | No | ||
| monthly_income_other | No | ||
| children_in_household | No | ||
| employer_house_number | No | ||
| preferred_loan_amount | No | ||
| total_number_of_loans | No | ||
| is_in_probation_period | No | ||
| monthly_income_alimony | No | ||
| monthly_income_pension | No | ||
| monthly_expense_alimony | No | ||
| preferred_loan_duration | No | ||
| total_monthly_debt_payment | No | ||
| working_at_current_job_since | No | ||
| living_at_current_address_since | No | ||
| monthly_expense_health_insurance | No | ||
| current_job_contract_is_limited_till | No | ||
| monthly_income_verifiable_additional | No | ||
| monthly_income_child_or_care_allowance | No | ||
| date_since_income_verifiable_additional | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| status | Yes | |
| response | Yes |
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the behavioral trait that this is a create operation, which is not explicitly stated in the annotations (they only provide openWorldHint=true, idempotentHint=false, destructiveHint=false). However, it does not disclose side effects, whether existing data is overwritten, authentication needs, or any other operational behavior. Given the annotations are present, the bar is lower, but the description still lacks depth.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that states the core purpose and the key requirement. Every word earns its place, and it is front-loaded with the action and resource. No fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having 54 parameters and an output schema, the description gives only a one-sentence overview. It does not mention prerequisites, side effects, or any operational context. While the output schema exists (so return values are covered), the tool's complexity demands a richer description to help an agent select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 54 parameters with zero property descriptions. The description groups them into 'personal, employment and financial data' and notes 'Only email is required', which adds some meaning. However, this is minimal compensation for the large, undocumented parameter set. It does not explain specific formats, constraints, or relationships between parameters beyond what the schema already encodes.
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 a specific action: 'Creates a MyWage user' with the supplied data. It names the resource (MyWage user) and scope (personal, employment, financial data), and clarifies the minimum requirement. While the title 'Transfer user' is somewhat ambiguous, the description resolves it by using the verb 'creates'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. 'Only email is required' is a parameter detail, not usage guidance. With no sibling tools listed, the description still fails to explicitly state the intended context or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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 or an account that owns the GitHub organization, then choose Claim with GitHub.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
Portable Roth IRA signups for gig workers: eligibility checks, signup initiation, partners, sandbox.
Hosted OAuth MCP for Google, Meta, X, and LinkedIn Ads, GA4, and Search Console.
Create and manage checkout pages, event ticketing, forms, customers, payments and subscriptions.
Collect and submit company incorporation requests for review by GVRN's corpsec team.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables employee information lookup, directory listing, payroll access, and time-off request management with Okta token validation.
HireFrog MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI assistants to securely access a user's job-search account, letting them search and save jobs, analyze job fit, and retrieve job queue and profile summaries with links back to the web app.MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to securely access an Invoice4U account for searching documents and customers and creating receipts linked to paid invoices, with read-only behavior by default.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.1/5.0
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The single tool has a clearly defined purpose as described.
Naming Consistency3/5
The name 'transfer_user' is misleading for a tool that creates a user, as 'transfer' implies moving funds rather than creating an account. However, with only one tool, there is no pattern to compare against.
Tool Count2/5
The server has only one tool, which feels very thin for a domain like money management. The scope of the server is unclear given the limited surface.
Completeness1/5
The server only supports creating a user, with no tools for payments, balances, transfers, or any other operations that would be expected for a money-related MCP. The surface is severely incomplete.