MCP servers observed by Lowdown
io.github.assinafy/mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 29 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.assinafy/mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.assinafy/mcp-server?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, server version changed
- 2026-11-13: input or output schemas changed, descriptions changed, server version changed
What tools does it list?
29 tools on 2026-11-16:
assinafy_browse_contractsassinafy_create_assignmentassinafy_create_document_from_templateassinafy_create_signerassinafy_delete_documentassinafy_download_documentassinafy_download_document_pageassinafy_get_documentassinafy_get_fieldassinafy_get_signerassinafy_get_templateassinafy_list_document_activitiesassinafy_list_documentsassinafy_list_fieldsassinafy_list_signersassinafy_list_templatesassinafy_list_whatsapp_notificationsassinafy_place_fieldsassinafy_rename_documentassinafy_resend_notificationassinafy_review_signature_requestassinafy_send_pdf_for_signatureassinafy_set_assignment_expirationassinafy_show_documentassinafy_update_contractassinafy_update_signerassinafy_upload_documentassinafy_validate_fieldsassinafy_verify_document
MCP Registry declaration
- Registry name:
io.github.assinafy/mcp-server - Declared version: 3.2.0
- Status: active
- Declared hosts:
mcp.assinafy.com.br
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.assinafy/mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.assinafy/mcp-server?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).