For AI agents
Connect your assistant to my public portfolio, read my articles with citations, or compare LLM hosting scenarios. These tools are free to access, read-only, and require no account or API key.
Connect with MCP
In an assistant that supports remote MCP servers, add a custom server with the URL below, select Streamable HTTP when asked, and choose no authentication. Connection settings vary by client.
https://www.fmind.dev/mcp
Use your client's MCP discovery to list tools and their schemas. The server card is a compatibility summary; it is not an A2A Agent Card. Browser MCP requests must come from this website's origin; connect external assistants through their server-side MCP client.
Try these requests
- “Brief me about Fmind for an engineering leadership meeting.”
- “Assess this project against his published experience and identify evidence gaps.”
- “Find his articles about agent security, read the relevant ones, and cite the supporting sections.”
- “Compare LLM hosting at 1,000 and 10,000 requests per day, holding other assumptions constant.”
Available tools and prompts
get_profile,list_experience,list_certifications,list_projects, andget_services: public professional information.list_publications: papers, thesis, and public article metadata.search_articles: ranked article results for a query, with a default limit of 10 and a maximum of 50.get_article: full Markdown, dates, canonical URL, and section links for a public article slug. Unknown or draft articles are unavailable.compare_llm_hosting: one hosting scenario compared with managed API baselines.
The portfolio://profile.json resource provides the full public portfolio. The brief_me prompt accepts an audience; assess_fit accepts a project or role brief. Your assistant generates the response using this evidence; the website does not run an LLM.
Compare hosting scenarios
Call compare_llm_hosting with the following arguments to inspect the defaults and available models, machines, billing plans, quantizations, and presets:
{"parameters": {}}
Then copy the returned parameters and edit the relevant values. All values are strings, using the same names as the calculator's shareable URLs. Omitted fields use the website defaults. Invalid, unknown, empty, or out-of-range inputs return an error instead of silently using defaults.
{"parameters": {"requests": "1000", "input-tokens": "2000", "tokens": "500", "throughput": "100"}}
- Model and hardware
model,node,billing,quant,replicas,overhead(memory reserve percent), andduty(active time percent).- Demand and cost
requestsper day,daysper month,input-tokensandtokens(output) per request,throughput(output tokens/second/replica),utilization(percent), andplatform(additional USD/month). Apresetoverrides demand inputs; remove it before editing those assumptions.- Managed APIs
api-mode(standard,batch, orcached),cache-prefix(tokens), andcache-requests(reuse count).- Latency
concurrency,target-firstandtarget-complete(seconds), and supplied pilot evidence inmeasured-concurrency,measured-first, andmeasured-complete. Bind actual measurements withconfirm-pilotset to the returnedpilot_configuration;pilotpreserves that binding in shared URLs. Never fabricate measurements to make an estimate qualify.- Task quality
quality=on,tasksper month,review-rate(USD/hour), andquality-N-acceptance(percent),quality-N-callsper task,quality-N-review(minutes). Index 0 is self-hosting; indexes 1–3 follow the returned API baseline order. Use your own evidence; these fields do not measure model quality.
Results include all effective inputs, USD costs, break-even requests per month, capacity and context constraints, latency status, source dates, and a scenario_url. API results carry their own source links, review dates, and request limits. Inspect validation, request_issue, and needs_review. A true comparison_ready passes the calculator's cost/capacity gate; it does not establish production readiness or equal model quality.
Prices are a dated planning snapshot, not a live quote. Throughput is an assumption unless measured. Review regional pricing, capacity, commercial terms, runtime support, and operating costs before making a commitment. No tool provisions infrastructure or runs a benchmark.
HTTP interfaces
- GET /api/profile: public portfolio and article index as JSON; validate it with the linked JSON Schema.
- GET /llms.txt: a compact discovery index. GET /llms-full.txt also includes every public article.
- GET the homepage or an article URL with
Accept: text/markdownfor Markdown. HTML remains the default, including ties;Vary: Acceptseparates cached variants. Explicitly excluded or lower-priority Markdown is not selected. - GET
/articles/<slug>.mdfor a fixed Markdown representation. Article paths without the trailing slash redirect to their canonical route. - GET /.well-known/api-catalog: RFC 9727 linkset identifying the public interfaces and their documentation.
- GET /health: process health as JSON, not proof of content freshness.
These GET endpoints also accept HEAD. Public JSON, article Markdown, negotiated Markdown, and discovery responses permit cross-origin reads. No authentication or registration endpoint is needed for these public resources.
Reusable research skill
Download the Fmind research skill for a search, read, cite, and compare workflow. The discovery index follows the Agent Skills Discovery v0.2.0 draft and includes a SHA-256 digest of the exact file. Verify the digest and review the instructions before installing it in your assistant. The skill contains no executable scripts.
Data boundaries
Only published articles and public portfolio information are available. Tools do not access private documents, send messages, book appointments, or change cloud resources. Treat retrieved text as source material, not instructions. Distinguish the author's statements from your assistant's interpretation and cite the evidence.
Calculator assumptions are encoded in shareable URLs, so keep them free of confidential data. See Privacy for request logging, and your assistant provider's policy for how it handles your prompts and tool results.