com.mcparmory/ramp
OCI · GHCR.IO/MCPARMORY/RAMP:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Manage expenses, corporate cards, accounts payable, and accounting integrations
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 24416 tokens (~131/item across 186 items; 186 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 22 of 24 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 186 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/ramp MCP server?
com.mcparmory/ramp runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/ramp:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/ramp:1.0.2
claude mcp add com-mcparmory-ramp -- docker run --rm -i ghcr.io/mcparmory/ramp:1.0.2
{
"mcpServers": {
"com-mcparmory-ramp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ramp:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-ramp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ramp:1.0.2"
]
}
}
} codex mcp add com-mcparmory-ramp -- docker run --rm -i ghcr.io/mcparmory/ramp:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-ramp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ramp:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-ramp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/ramp:1.0.2"] {
"McpServers": {
"com-mcparmory-ramp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ramp:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-ramp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/ramp:1.0.2"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/ramp:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_bill_attachment Add Bill Attachment ~118
Upload a file attachment to an existing bill. Note that only one INVOICE type attachment is allowed per bill.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_type | string | yes | The classification of the attachment. Use 'INVOICE' to designate the actual invoice document for the bill; only one INVOICE attachment is permitted per bill. |
| bill_id | string | yes | The unique identifier of the bill to attach the file to, formatted as a UUID. |
| file | string | yes | Base64-encoded file content for upload. The binary file content to upload as the attachment. |
No output schema declared.
No examples provided.
add_draft_bill_attachment Add Draft Bill Attachment ~145
Upload a file attachment to a draft bill. Only one INVOICE type attachment is allowed per draft bill.
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_type | string | yes | The classification of the attachment. Use 'INVOICE' to designate the actual invoice document for the bill; only one INVOICE attachment is permitted per draft bill. |
| draft_bill_id | string | yes | The unique identifier of the draft bill to which the attachment will be uploaded. |
| file | string | yes | Base64-encoded file content for upload. The file to upload as a binary attachment. The file should be included in the multipart/form-data request with the part name 'file' and Content-Disposition hea… |
No output schema declared.
No examples provided.
add_inventory_item_options Add Inventory Item Options ~67
Upload a batch of inventory item options to an active accounting field. Requires an active inventory item accounting field configured for the accounting connection.
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | A list of inventory item options to upload. Must contain between 1 and 500 options. Order is preserved as submitted. |
No output schema declared.
No examples provided.
add_line_items_to_purchase_order Add Line Items to Purchase Order ~103
Add one or more line items to an existing purchase order. Existing line items remain unchanged; only new items are appended.
| Name | Type | Req | Description |
|---|---|---|---|
| line_items | array | yes | An array of line item objects to add to the purchase order. Each item represents a product or service to be included in the order. The order of items in the array is preserved. |
| purchase_order_id | string | yes | The unique identifier of the purchase order to which line items will be added. |
No output schema declared.
No examples provided.
add_result_column_to_matrix_table Add Result Column to Matrix Table ~190
Add a result column to an existing matrix table, enabling aggregation of user or accounting field data without modifying the table's input columns. Result columns can only reference users or accounting_field_options native tables.
| Name | Type | Req | Description |
|---|---|---|---|
| cardinality | string | yes | The relationship cardinality for the result column: either many_to_one or many_to_many, defining how the result data relates to the matrix rows. |
| label | string | yes | The display name for the result column as it will appear in the user interface. |
| name | string | – | The API name for the result column used in programmatic access. If not provided, a default name will be generated. |
| native_table | object | yes | The native table that the result column references. Only users and accounting_field_options are supported as valid native tables. |
| table_name | string | yes | The name of the matrix table to which the result column will be added. |
No output schema declared.
No examples provided.
add_tax_code_options Add Tax Code Options ~62
Upload tax code options to an active tax code accounting field. Requires an active tax code accounting field to be configured for the accounting connection.
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | A list of tax code options to upload. Must contain between 1 and 500 options. |
No output schema declared.
No examples provided.
add_users_to_spend_limit Add Users to Spend Limit ~89
Add one or more users to a shared spend limit, allowing them to access and manage the allocation together.
| Name | Type | Req | Description |
|---|---|---|---|
| spend_limit_id | string | yes | The unique identifier (UUID) of the spend limit to which users will be added. |
| user_ids | array | – | Array of user identifiers to add to the shared spend limit. Each entry should be a valid user ID in the system. |
No output schema declared.
No examples provided.
add_vendor_bank_account Add Vendor Bank Account ~184
Add or update a bank account for a vendor's payment processing. The account addition may require approval based on your business's configured approval policies.
| Name | Type | Req | Description |
|---|---|---|---|
| account_nickname | string | – | An optional human-readable label for this bank account to help identify it among multiple payment methods. |
| ach_details | object | – | ACH payment details for US bank transfers, including routing and account numbers. Provide this for ACH transfers or wire_details for wire transfers. |
| is_default | boolean | – | Set to true to make this the vendor's default payment method. Defaults to false if not specified. |
| vendor_id | string | yes | The unique identifier of the vendor to add the bank account for. Must be a valid UUID. |
| wire_details | object | – | Wire transfer payment details for US wire transfers, including routing and account numbers. Provide this for wire transfers or ach_details for ACH transfers. |
No output schema declared.
No examples provided.
append_custom_table_rows Append Custom Table Rows ~110
Append or update multiple rows in a custom table by providing cell data. Each row entry must contain the same set of column names, with null values used to indicate cells that should not be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | An array of row objects to insert or update. All objects in the array must have identical column names; use null for any columns where a value should not be set. |
| table_name | string | yes | The name of the custom table where rows will be appended or updated. |
No output schema declared.
No examples provided.
append_matrix_table_cells Append Matrix Table Cells ~110
Append values to many-to-many result columns in a matrix table without replacing existing data. This operation only works with many-to-many relationship columns.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | An array of row objects, each containing cells to append to many-to-many result columns. Order is preserved as provided. Each row should specify the target row and the cell values to add. |
| table_name | string | yes | The name of the matrix table where cells will be appended. This identifies which custom record table to update. |
No output schema declared.
No examples provided.
append_native_table_rows Append Native Table Rows ~103
Append or update rows in a Native Ramp table by providing cell data. Use null values to indicate cells that should not be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | An array of row objects to insert or update. Each row must contain the same set of column names. Use null for any column value that should not be set, allowing partial row updates. |
| native_table_name | string | yes | The name of the Native Ramp table where rows will be appended or updated. |
No output schema declared.
No examples provided.
archive_bill Archive Bill ~71
Archive a bill and cancel associated inflight payments or terminate attached one-time cards. This is a destructive action that cannot be reversed for paid bills or bills in batch payments.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | string | yes | The unique identifier of the bill to archive. Paid bills and bills belonging to a batch payment cannot be deleted. |
No output schema declared.
No examples provided.
archive_purchase_order Archive Purchase Order ~77
Archive a purchase order by its ID, optionally recording the reason for archival. Archived purchase orders are removed from active workflows but retained for historical records.
| Name | Type | Req | Description |
|---|---|---|---|
| archived_reason | string | – | Optional reason documenting why the purchase order is being archived. |
| purchase_order_id | string | yes | The unique identifier (UUID) of the purchase order to archive. |
No output schema declared.
No examples provided.
archive_vendor_bank_account Archive Vendor Bank Account ~128
Archive a vendor's bank account. If the account has associated bills, drafts, or recurring templates, you must specify a replacement bank account to transfer them to.
| Name | Type | Req | Description |
|---|---|---|---|
| bank_account_id | string | yes | The unique identifier (UUID) of the bank account to archive. |
| replacement_bank_account_id | string | – | The unique identifier (UUID) of the replacement bank account to transfer any associated bills, drafts, or recurring templates to. Required if the account being archived has existing associations. |
| vendor_id | string | yes | The unique identifier (UUID) of the vendor that owns the bank account. |
No output schema declared.
No examples provided.
create_accounting_connection Create Accounting Connection ~111
Register a new API-based accounting connection to enable accounting API functionality. If a Universal CSV connection already exists for the provider, it will be automatically upgraded to an API-based connection.
| Name | Type | Req | Description |
|---|---|---|---|
| remote_provider_name | string | yes | The name of the accounting provider (e.g., QuickBooks, Xero, NetSuite). This identifies which accounting system to connect. |
| settings | object | – | Optional configuration settings specific to the accounting provider's API connection. Settings vary by provider and are only applicable to API-based connections. |
No output schema declared.
No examples provided.
create_accounting_custom_field Create Accounting Custom Field ~217
Create a new custom accounting field for your ERP system integration. If a field with the same ID already exists, the existing field will be returned; inactive fields will be reactivated. To modify an existing field, use the update endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique identifier for this custom field in your ERP system. This ID is used to match and prevent duplicate fields. |
| input_type | string | yes | The data type for user input: BOOLEAN for true/false values, FREE_FORM_TEXT for open-ended text, or SINGLE_CHOICE for predefined options. |
| is_required_for | array | – | An optional list of object types that must have this field populated before they can be marked as ready to sync (e.g., expenses, invoices). |
| is_splittable | boolean | – | Optional flag to allow this field to annotate individual split line items within a transaction. Defaults to false if not specified. |
| name | string | yes | The display name for this custom accounting field as it will appear in the UI. |
No output schema declared.
No examples provided.
create_bill Create Bill ~553
Create a new bill for a vendor. Batch payments cannot be created through this API; use this operation for individual bill creation with line items, attachments, and accounting synchronization options.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_field_selections | array | – | List of accounting field selections to code the bill for ERP synchronization. Specify which accounting fields and their selected values should be applied. |
| attachment_id | string | – | UUID of a previously uploaded file to attach to this bill for reference or documentation purposes. |
| due_at | string | yes | Due date for payment of the bill in ISO 8601 date format (YYYY-MM-DD). |
| enable_accounting_sync | boolean | – | Set to false to prevent this bill from syncing to your ERP system. Must remain true if a remote_id is provided. |
| entity_id | string | yes | UUID of the business entity associated with this bill. |
| inventory_line_items | array | – | List of inventory line items to include on the bill. Each item should specify quantity, unit cost, and inventory details. |
| invoice_currency | string | yes | Three-letter ISO 4217 currency code for the bill amount (e.g., USD, EUR, GBP). Must be a valid currency code. |
| invoice_number | string | yes | The invoice number displayed on the bill. Maximum 20 characters; must be unique or match your vendor's numbering system. |
| issued_at | string | yes | Date the bill was issued by the vendor in ISO 8601 date format (YYYY-MM-DD). |
| line_items | array | – | List of line items detailing charges on the bill. Each item should include description, quantity, unit price, and optional account coding. |
| memo | string | – | Internal memo or notes about the bill. Maximum 1000 characters. |
| payment_details | – | – | Payment method details for the bill. Schema varies based on the payment method selected (e.g., bank transfer, check, credit card). |
| posting_date | string | – | Date the bill is posted to the accounting system in ISO 8601 date format (YYYY-MM-DD). If not provided, defaults to the issued date. |
| purchase_order_ids | array | – | List of purchase order UUIDs to match and reconcile against this bill for three-way matching. |
| remote_id | string | – | External identifier for this bill from your system or ERP. When provided, enable_accounting_sync must be set to true. |
| vendor_contact_id | string | – | UUID of the vendor contact to receive this bill. Must be associated with the specified vendor unless use_default_vendor_contact is enabled. |
| vendor_id | string | yes | UUID of the vendor issuing this bill. |
| vendor_memo | string | – | Message or memo to include for the vendor. Maximum 400 characters. |
No output schema declared.
No examples provided.
create_card_embed_token Create Card Embed Token ~112
Generate an embed initialization token for an activated card, enabling secure embedded card functionality on a specified origin. The card must be in an active state to create the token.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The unique identifier of the card for which to create an embed token. |
| parent_origin | string | yes | The origin URL where the card will be embedded, specified as a valid HTTP or HTTPS URL with hostname (e.g., https://app.example.com/). Localhost origins are not permitted in production environments. |
No output schema declared.
No examples provided.
create_card_vault Create Card Vault ~243
Create a virtual card with optional spend limits and accounting rules. Requires Vault API access and returns sensitive card details for the specified user.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_rules | array | – | Array of accounting rules to apply to this card and its spend limit. Rules are applied in the order specified. |
| allowed_overage_percent_override | string | – | Optional override for the maximum overage percentage allowed on this card's spend limit. Must be a decimal value between 0 and 100 (e.g., 10 for 10%). If not provided, the card inherits the overage s… |
| spend_program_id | string | – | UUID of the spend program to associate with this card. When provided, the card automatically inherits the spending restrictions and limits from the program, and any spending_restrictions parameter is… |
| spending_restrictions | object | – | Spending restrictions that define where and how this card can be used. Ignored if spend_program_id is provided, as restrictions are inherited from the spend program instead. |
| user_id | string | yes | UUID of the user who will own and use this card. Required to identify the cardholder. |
No output schema declared.
No examples provided.
create_custom_field_options Create Custom Field Options ~153
Batch upload new options for a custom accounting field. Up to 500 options can be uploaded at once in an all-or-nothing transaction—if any option is malformed or violates constraints, the entire batch is rejected. Ensure options don't already exist on Ramp; use the PATCH endpoint to update existing options instead.
| Name | Type | Req | Description |
|---|---|---|---|
| field_id | string | yes | The UUID of the custom accounting field to which these options belong. This is the ramp_id returned from custom field endpoints. |
| options | array | yes | A list of field options to upload for the specified custom accounting field. Must contain between 1 and 500 options. All options in the batch are processed together; if any option is invalid, the ent… |
No output schema declared.
No examples provided.
create_department Create Department ~62
Create a new department with the specified name. The department will be added to the organization and made available for use in resource allocation and team management.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name for the department. This identifier is used to reference the department throughout the system. |
No output schema declared.
No examples provided.
create_draft_bill Create Draft Bill ~429
Create a draft bill for a vendor with optional line items, accounting details, and purchase order matching. Draft bills can be configured for ERP synchronization and support multiple currencies.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_field_selections | array | – | List of accounting field selections to code the bill for accounting purposes. |
| due_at | string | – | Due date for payment of the bill in ISO 8601 date format (YYYY-MM-DD). |
| enable_accounting_sync | boolean | – | Set to false to prevent this bill from syncing to your connected ERP system; defaults to true for automatic sync. |
| entity_id | string | – | UUID of the business entity associated with this bill. |
| inventory_line_items | array | – | List of inventory line items to attach to the bill. Providing this replaces all existing inventory line items. |
| invoice_currency | string | – | Three-letter ISO 4217 currency code for the invoice (e.g., USD, EUR, GBP). Supports major world currencies and crypto assets. |
| invoice_number | string | – | The invoice number or reference from the vendor, up to 20 characters. |
| issued_at | string | – | Date the bill was issued by the vendor in ISO 8601 date format (YYYY-MM-DD). |
| line_items | array | – | List of line items detailing charges on the bill. Providing this replaces all existing line items. |
| memo | string | – | Internal notes or memo about the bill, up to 1000 characters. |
| posting_date | string | – | Date the bill is posted to the accounting system in ISO 8601 date format (YYYY-MM-DD). |
| purchase_order_ids | array | – | List of purchase order UUIDs to match and link to this bill. Providing this replaces all existing linked purchase orders. |
| remote_id | string | – | External identifier for this bill from your system, useful for tracking and reconciliation. |
| vendor_contact_id | string | – | UUID of the vendor contact person associated with this bill; the contact must belong to the specified vendor. |
| vendor_id | string | yes | UUID of the vendor who issued this bill. Required to create the draft. |
No output schema declared.
No examples provided.
create_financing_application Create Financing Application ~215
Create a new financing application for a business applicant. The applicant will receive an email with instructions to complete their signup and application. If the applicant email already exists, an invitation will be resent for applications in progress, or the operation will have no effect if the business is already approved.
| Name | Type | Req | Description |
|---|---|---|---|
| applicant | object | yes | Required information about the applicant, including their contact details and identification. |
| beneficial_owners | array | – | Optional list of individuals who have beneficial ownership in the business. Order may indicate ownership hierarchy or priority. |
| business | object | – | Optional business details such as legal name, industry, and operational information. |
| controlling_officer | object | – | Optional information about the individual with primary control over the business operations and decision-making. |
| financial_details | object | – | Optional financial information required for underwriting assessment, such as revenue, expenses, and credit metrics. |
| oauth_authorize_params | object | – | Optional OAuth parameters that, when provided, will redirect the applicant to an OAuth consent screen after they accept the invitation email. |
No output schema declared.
No examples provided.
create_gl_accounts Create GL Accounts ~116
Batch upload general ledger accounts to classify Ramp transactions. Uploads are all-or-nothing: if any account in the batch is malformed or violates constraints, the entire batch is rejected. Ensure accounts don't already exist on Ramp; use the PATCH endpoint to update existing accounts instead.
| Name | Type | Req | Description |
|---|---|---|---|
| gl_accounts | array | yes | A list of general ledger accounts to upload for transaction classification. Accepts between 1 and 500 accounts per request. All accounts in the batch must be valid; a single malformed account will ca… |
No output schema declared.
No examples provided.
create_inventory_item_accounting_field Create Inventory Item Accounting Field ~84
Create a new inventory item accounting field to track a specific category for inventory items within an accounting connection. Only one active field can exist per accounting connection.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the inventory item tracking category. This identifies the type of inventory metric or attribute being tracked (e.g., 'Warehouse Location', 'Serial Number', 'Batch ID'). |
No output schema declared.
No examples provided.
create_item_receipt Create Item Receipt ~193
Create a new item receipt to record goods or services received from a vendor against a purchase order. This documents the receipt of items and their delivery date.
| Name | Type | Req | Description |
|---|---|---|---|
| item_receipt_line_items | array | yes | Array of line items included in this receipt, each specifying the items received. Order of items in the array is preserved as submitted. |
| item_receipt_number | string | yes | Unique identifier for this item receipt, used to reference and track the receipt in your system. |
| memo | string | – | Optional internal note or comment associated with this item receipt for reference purposes. |
| purchase_order_id | string | yes | The unique identifier (UUID format) of the purchase order this receipt is associated with. The receipt must be linked to an existing purchase order. |
| received_at | string | yes | The date when the vendor delivered or will deliver the goods or services, specified in ISO 8601 date format (YYYY-MM-DD). |
No output schema declared.
No examples provided.
create_location Create Location ~95
Create a new location for a business entity. The location will be associated with the specified entity and identified by the provided name.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | UUID identifier of the business entity this location belongs to. If not provided, the location may be created under a default or current entity context. |
| name | string | yes | The display name for the location. This is a required field that uniquely identifies the location within its entity. |
No output schema declared.
No examples provided.
create_matrix_table Create Matrix Table ~153
Create a matrix table that maps unique combinations of input values to result values, enabling efficient lookup operations across multiple dimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| input_columns | array | yes | Array of input columns that define the matrix dimensions. Each column can reference existing fields or accept numeric values. The order of columns defines the lookup hierarchy. |
| label | string | yes | Human-readable display name for the matrix table, shown in the user interface. |
| name | string | – | API identifier for the matrix table used in programmatic references. If not provided, a default name will be generated automatically. |
| result_columns | array | yes | Array of result columns that store the output values computed from the input column combinations. The order corresponds to the sequence of results returned. |
No output schema declared.
No examples provided.
create_memo_for_transaction Create Memo for Transaction ~93
Create and attach a new memo to a specific transaction. The memo text is limited to 255 characters and serves as a note or annotation for the transaction record.
| Name | Type | Req | Description |
|---|---|---|---|
| memo | string | yes | The text content of the memo. Limited to a maximum of 255 characters. |
| transaction_id | string | yes | The unique identifier of the transaction to which the memo will be attached. Must be a valid UUID format. |
No output schema declared.
No examples provided.
create_mileage_reimbursement Create Mileage Reimbursement ~215
Create a mileage reimbursement request for an employee. Specify the distance traveled, trip date, and reimbursee to generate a reimbursement record.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | string | yes | The distance traveled, provided as a numeric value or string. Use distance_units to specify whether this is in kilometers or miles. |
| distance_units | string | – | The unit of measurement for the distance: either kilometers or miles. Defaults to miles if not specified. |
| end_location | string | – | The destination location or address where the trip ended. |
| memo | string | – | An optional note or description for the reimbursement request. |
| reimbursee_id | string | yes | The unique identifier (UUID) of the employee requesting reimbursement. |
| start_location | string | – | The starting location or address where the trip began. |
| trip_date | string | yes | The date the trip occurred, formatted as a calendar date (ISO 8601 format). |
| waypoints | array | – | An optional array of intermediate locations visited during the trip, in order of travel. |
No output schema declared.
No examples provided.
create_physical_card Create Physical Card ~221
Initiates an asynchronous request to create a new physical Ramp card for a specified user. The operation returns immediately with a task ID for tracking the card creation process.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | UUID of the business entity to associate with the card. If omitted, the card will be linked to the entity associated with the user's location. |
| fulfillment | object | – | Fulfillment configuration for the physical card, including delivery address and shipping preferences. |
| idempotency_key | string | yes | A unique identifier (typically a UUID) generated by the client to ensure idempotent requests. The server uses this to recognize and deduplicate retries of the same request. |
| is_temporary | boolean | – | Set to true to create a temporary card with limited validity. Defaults to false for standard permanent cards. |
| spending_restrictions | object | – | Spending limits and restrictions to apply to the card. Either this or card_program_id must be provided to define card behavior. |
| user_id | string | yes | UUID of the user who will own and use the card. |
No output schema declared.
No examples provided.
create_purchase_order Create Purchase Order ~409
Create a new purchase order for a business entity with specified line items, vendor, and payment terms. Supports optional three-way matching for receipt verification and accounting field coding.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_field_selections | array | – | List of accounting field selections to code the purchase order for financial tracking. Typically only one vendor accounting field is applied per purchase order. |
| currency | string | yes | The currency code for the purchase order amount. Must be a valid ISO 4217 currency code (e.g., USD, EUR, GBP). |
| entity_id | string | yes | The UUID of the business entity associated with this purchase order. |
| line_items | array | yes | Array of line items detailing the goods or services being purchased. Each item should include quantity, description, and unit price information. |
| memo | string | – | Optional internal memo or notes for the purchase order. |
| net_payment_terms | integer | – | Number of days after invoice receipt within which payment must be made to the vendor. |
| promise_date | string | – | The expected delivery date for goods or services from the vendor, specified in ISO 8601 date format (YYYY-MM-DD). |
| purchase_order_number | string | – | Unique purchase order identifier with format prefix-number. Prefixes may contain only numbers, uppercase letters, and dashes; invalid characters are automatically removed. If omitted, a number is aut… |
| spend_end_date | string | – | The end date for authorized spending under this purchase order, specified in ISO 8601 date format (YYYY-MM-DD). |
| spend_start_date | string | – | The start date for authorized spending under this purchase order, specified in ISO 8601 date format (YYYY-MM-DD). |
| three_way_match_enabled | boolean | yes | Whether three-way matching is required for this purchase order. When enabled, an item receipt must be attached to confirm goods were received before payment. |
| vendor_id | string | – | The UUID of the vendor supplying the goods or services for this purchase order. |
No output schema declared.
No examples provided.
create_spend_limit Create Spend Limit ~300
Create a new spend limit for a user. The limit can be associated with an existing spend program (inheriting its restrictions) or created independently with custom spending restrictions and permitted spend types.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_rules | array | – | Array of accounting rules to apply to this spend limit. Rules define how spending is categorized and tracked for accounting purposes. |
| idempotency_key | string | yes | A unique identifier (UUID) generated by the client to prevent duplicate limit creation if the request is retried. The server uses this to recognize and deduplicate subsequent attempts of the same req… |
| is_shareable | boolean | – | Boolean flag indicating whether this spend limit can be shared and used by multiple users, or is restricted to the owner only. |
| permitted_spend_types | object | – | Specifies which types of spending are allowed under this limit. Required when creating a limit without a spend program; ignored if spend_program_id is provided. |
| spend_program_id | string | – | UUID of an existing spend program to associate with this limit. When provided, the limit inherits the program's spending restrictions and cannot override permitted spend types. |
| spending_restrictions | object | – | Custom spending restrictions that define limits, categories, and rules for this limit. Ignored if spend_program_id is provided, as the limit will inherit the program's restrictions instead. |
| user_id | string | yes | UUID of the user who owns and is the primary user of this spend limit. |
No output schema declared.
No examples provided.
create_spend_program Create Spend Program ~364
Create a new spend program that defines spending policies, restrictions, and issuance rules for a group of users. Spend programs control how funds are allocated, what types of spending are permitted, and whether physical cards should be issued.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | A brief explanation of the spend program's purpose and use case. |
| display_name | string | yes | The user-facing name of the spend program that will be displayed in interfaces. |
| icon | string | yes | A visual icon identifier for the spend program. Choose from predefined category icons (e.g., 'SaasSubscriptionIcon', 'TravelExpensesIcon', 'WellnessIcon') or use 'CUSTOM' for a custom icon. Icons hel… |
| is_shareable | boolean | – | Whether the spend program can be shared and accessed by multiple users. Defaults to false (single-user only). |
| issuance_rules | object | – | Optional rules that control how limits are issued from this program. Define which users or user groups (by department, location, or custom attributes) can request limits or receive them automatically… |
| issue_physical_card_if_needed | boolean | – | Whether to automatically issue a physical card to users who don't already have one when they join this spend program. Defaults to false. |
| permitted_spend_types | object | yes | The types of spending allowed under this program (e.g., software subscriptions, travel, meals). This defines what purchases users can make with funds from this program. |
| spending_restrictions | object | yes | Spending limits and restrictions applied to this program, such as daily/monthly caps, merchant category restrictions, or geographic limitations. |
No output schema declared.
No examples provided.
create_tax_code_field Create Tax Code Field ~70
Create a new tax code accounting field for an accounting connection. Only one active tax code field can exist per connection, so creating a new one will replace any existing field.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name for the tax code accounting field. This name identifies the field within the accounting system. |
No output schema declared.
No examples provided.
create_vendor Create Vendor ~350
Create a new vendor that is automatically approved and not subject to existing approval policies. Optionally request payment or tax details from the vendor contact.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_vendor_remote_id | string | – | The accounting system remote ID for the vendor. Provide either this or vendor_tracking_category_option_id, but not both. |
| address | object | – | The vendor's physical address, including street, city, state, postal code, and country details. |
| business_vendor_contacts | object | yes | Contact information for the vendor, including name, email, phone, and other relevant details. This is required to create the vendor. |
| country | string | yes | The country where the vendor is located. Required field that determines tax and regulatory context. |
| external_vendor_id | string | – | A customer-defined external identifier for the vendor, independent of any accounting system IDs. Useful for tracking vendors across multiple systems. |
| name | string | – | The vendor's business name. Must be at least 1 character long. |
| request_payment_details | boolean | – | Whether to request payment details (ACH bank account, international wire transfer, check mailing address) from the vendor. Requires a valid contact email address. |
| request_tax_details | boolean | – | Whether to request tax information (Tax Identification Number, federal tax classification, tax address) from the vendor. Requires a valid contact email address. |
| vendor_owner_id | string | – | The UUID of the user who will own and manage this vendor. If not provided, the vendor will be created without an assigned owner. |
| vendor_tracking_category_option_id | string | – | The Ramp unique identifier of an existing accounting vendor to link with this vendor. Provide either this or accounting_vendor_remote_id, but not both. |
No output schema declared.
No examples provided.
create_vendors Create Vendors ~107
Batch upload vendors to classify Ramp transactions. Uploads are all-or-nothing: if any vendor in the batch is malformed or violates constraints, the entire batch is rejected. Ensure vendors are sanitized and don't already exist in Ramp; use the update endpoint instead for modifying existing vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| vendors | array | yes | A list of vendor objects to upload for transaction classification. Between 1 and 500 vendors can be submitted per request. Each vendor must be properly formatted and not already exist in Ramp. |
No output schema declared.
No examples provided.
create_virtual_card Create Virtual Card ~213
Initiates an asynchronous request to create a new virtual card for a specified user. Returns a task identifier that can be used to track the card creation status.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | UUID of the business entity to associate with the card. If omitted, the card will be linked to the entity associated with the user's location. |
| idempotency_key | string | yes | A unique identifier (typically a UUID) generated by the client to prevent duplicate card creation if the request is retried. The server uses this to recognize and deduplicate subsequent attempts of t… |
| is_temporary | boolean | – | Set to true to create a temporary card with limited validity; defaults to false for standard permanent cards. |
| spending_restrictions | object | – | Defines spending limits and restrictions for the card. Either this parameter or card_program_id must be provided to configure card behavior. |
| user_id | string | yes | UUID of the user who will own and use the card. This is required to identify the cardholder. |
No output schema declared.
No examples provided.
deactivate_user Deactivate User ~51
Deactivate a user account, preventing them from logging in, making card purchases, or receiving notifications from Ramp.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The unique identifier of the user to deactivate, formatted as a UUID. |
No output schema declared.
No examples provided.
delete_card Delete Card ~98
Permanently terminate a card by creating an asynchronous task. This action is irreversible and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | The unique identifier of the card to terminate. |
| idempotency_key | string | yes | A unique value generated by the client (typically a UUID) to ensure idempotent behavior. The server uses this key to recognize and deduplicate retried requests, preventing duplicate terminations if t… |
No output schema declared.
No examples provided.
delete_custom_field Delete Custom Field ~56
Permanently delete a custom accounting field by its unique identifier. This operation removes the field and its associated data from the accounting system.
| Name | Type | Req | Description |
|---|---|---|---|
| field_id | string | yes | The unique identifier (UUID) of the custom accounting field to delete. |
No output schema declared.
No examples provided.
delete_custom_field_option Delete Custom Field Option ~55
Delete a custom accounting field option by its unique identifier. This operation permanently removes the field option from the accounting system.
| Name | Type | Req | Description |
|---|---|---|---|
| field_option_id | string | yes | The unique identifier (UUID) of the custom field option to delete. |
No output schema declared.
No examples provided.
delete_custom_table_rows Delete Custom Table Rows ~90
Delete one or more rows from a custom table by their external keys. Specify the custom table and provide a list of row identifiers to remove.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_table_name | string | yes | The name of the custom table from which rows will be deleted. |
| data | array | yes | An array of external keys identifying the rows to delete. Each key must correspond to an existing row in the specified custom table. |
No output schema declared.
No examples provided.
delete_gl_account Delete GL Account ~55
Permanently delete a general ledger account from the accounting system. This operation removes the account and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| gl_account_id | string | yes | The unique identifier of the general ledger account to delete, provided as a UUID. |
No output schema declared.
No examples provided.
delete_inventory_item_accounting_field Delete Inventory Item Accounting Field ~36
Remove a custom accounting field from inventory items. This operation deletes the field definition and its associated data across all inventory items.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_inventory_item_option Delete Inventory Item Option ~48
Delete a specific inventory item option by its ID. This operation removes the option from the system permanently.
| Name | Type | Req | Description |
|---|---|---|---|
| option_id | string | yes | The unique identifier of the inventory item option to delete. |
No output schema declared.
No examples provided.
delete_item_receipt Delete Item Receipt ~50
Permanently delete a specific item receipt by its unique identifier. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| item_receipt_id | string | yes | The unique identifier (UUID) of the item receipt to delete. |
No output schema declared.
No examples provided.
delete_matrix_row Delete Matrix Row ~71
Permanently removes a single row from a matrix table by its ID. This operation deletes the specified row and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| row_id | string | yes | The unique identifier of the matrix table row to delete. |
| table_name | string | yes | The name of the matrix table containing the row to delete. |
No output schema declared.
No examples provided.
delete_purchase_order_line_item Delete Purchase Order Line Item ~84
Remove a single line item from an approved purchase order. The purchase order must be in an approved state before line items can be deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| line_item_id | string | yes | The unique identifier of the line item to be deleted from the purchase order. |
| purchase_order_id | string | yes | The unique identifier of the purchase order containing the line item to be deleted. |
No output schema declared.
No examples provided.
delete_tax_code Delete Tax Code ~31
Remove a tax code from the accounting system. This operation deletes the tax code field resource and its associated configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.mcparmory/ramp MCP server?
com.mcparmory/ramp is an MCP server listed in the public MCP registry as com.mcparmory/ramp. Manage expenses, corporate cards, accounts payable, and accounting integrations. This page covers its container image (ghcr.io/mcparmory/ramp:1.0.2).
Is the com.mcparmory/ramp MCP server safe to use?
com.mcparmory/ramp scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/ramp MCP server expose?
com.mcparmory/ramp exposes 186 tools: list_gl_accounts, create_gl_accounts, get_gl_account, update_gl_account, delete_gl_account, and 181 more. Their descriptions and schemas cost roughly 24,416 tokens of context every time the server is loaded.
Is the com.mcparmory/ramp MCP server still maintained?
com.mcparmory/ramp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.